[dotnet-watch] Simplify logging #51307
Open
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 was referenced Nov 10, 2025
Member
Author
|
@DustinCampbell ptal |
DustinCampbell
approved these changes
Dec 9, 2025
3 tasks
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.
Remove MessageSererity and Verbose, Quiet flags and use LogLevel uniformly.
Default level is
LogLevel.Information.--verboseflag setsLogLevel.Debug.--quietflag setsLogLevel.Warning.Enable turning on
Tracelogging level viaDOTNET_CLI_CONTEXT_VERBOSEenv variable for extra detailed logging that may have impact on performance (previously only reported inDEBUGbuilds).Currently, dotnet-watch parses
DOTNET_CLI_CONTEXT_VERBOSEenv variable as a boolean value that turns on verbose logging. Addtraceas an additional recognized value that sets logging level toLogLevel.Trace.