To ensure a clean build state and resolve transient compilation issues, follow this process:
- •
Stop Background Processes
- •Ensure no background
dotnetprocesses are running that might lock files. - •Check for running Aspire instances or test hosts.
- •Ensure no background
- •
Clean Solution
- •Run
dotnet cleanin the root directory. - •This removes all intermediate output and binaries.
- •Run
// turbo 3. Rebuild
- •Run
dotnet buildin the root directory to compile the entire solution from scratch.
- •Verify and Report
- •Check the output for any persistent errors.
- •If the build succeeds, notify the user: "✅ Workspace is clean and builds successfully."
- •If errors persist, they are likely genuine code issues rather than stale artifacts.
- •Use
grep_searchorread_fileto investigate the specific error messages.
When to Use
- •Build errors that seem inconsistent
- •After major dependency changes
- •When switching branches with significant changes
- •Stale artifact issues
- •After package version updates
Related Skills
Used By:
- •
/verify-feature- May reference this for clean builds
Next Steps:
- •
/verify-feature- Full verification after clean rebuild - •
/run-unit-testsor/run-integration-tests- Test the rebuilt solution
See Also:
- •getting-started - Build instructions
- •aspire-guide - Running the application