[dotnet-watch] Remove excess logging that slows down Hot Reload #51220
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.
Description
Remove logging of solution content in Release builds. This logging used to be valuable for diagnostics in past, but we haven't seen issues that need this information in a while.
The logging slows down project loading.
Customer Impact
Significantly improves dotnet-watch initialization, especially on large solutions.
On a solution with 4,500 files the project load time is reduced by 75s (46%): from 164s to 89s.
Regression?
Regression compared to 8.0. The logging was added in 9.0.
Risk
Justification: The impact is limited to sending Hot Reload messages to browser and the change is trivial.
Verification
Packaging changes reviewed?