Improve progress output, rebuild projects serially #51227
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR is targeting |
This was referenced Oct 13, 2025
…g multiple projects
Open
3 tasks
|
@DustinCampbell ptal |
tmat
changed the title
DustinCampbell
approved these changes
Oct 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only capture output of
dotnet buildwhen running in a test environment. In production, letdotnet buildshow build progress.Output messages that inform of project evaluation start and end, and project load start and end, and include elapsed time.
Output "Waiting for changes" even when
--verboseis not specified, so that it's clear when dotnet-watch starts to listen for changes.When projects need to be rebuilt due to rude edits, rebuild them serially to avoid potential write access issues of dependent project outputs.