What problem does it solve?
Building the WinForms repository correctly requires the Arcade build system, not a plain dotnet build, because only build.cmd applies the CI analyzers, PublicAPI checks, and warn-as-error settings that determine whether a change actually passes the official build.
Core Features & Use Cases
- Guided restore and full builds: Runs Restore.cmd and build.cmd with the repo-local SDK pinned in global.json, including clean, release, and packaging workflows.
- Fast inner-loop builds: Builds a single project with dotnet build for quick iteration after an initial full restore.
- Troubleshooting support: Diagnoses build errors using binary logs in artifacts\log and the MSBuild Structured Log Viewer.
- Use Case: After editing System.Windows.Forms source code, run a single-project build to iterate quickly, then verify with build.cmd before claiming the change compiles cleanly in CI.
Quick Start
Ask the assistant to restore and build the WinForms solution with build.cmd and report which assemblies succeeded or failed.