Skip to content

Clarify --verbosity usage in dotnet build #48889

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Clarify --verbosity usage in dotnet build #48889

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dce2cc3
clarify verbosity in terminallogger
JanProvaznik Oct 3, 2025
7d09c46
Update docs/core/tools/dotnet-build.md
JanProvaznik Oct 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/core/tools/dotnet-build.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,7 @@ Running `dotnet build` is equivalent to running `dotnet msbuild -restore`; howev

- **`-v|--verbosity <LEVEL>`**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JanProvaznik one thing I've been doing for options that are used across multiple commands is to use and reference includes files. I have an open PR out doing cleanup like that across the commands: https://github.com/dotnet/docs/pull/48787/files.

Could you update the includes file at: ../../../includes/cli-verbosity.md with your updated description and link to that here instead?

Suggested change
- **`-v|--verbosity <LEVEL>`**
`[!INCLUDE [verbosity](../../../includes/cli-verbosity.md)]`

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@meaghanlewis @JanProvaznik this note would only be valid for dotnet CLI commands that use MSBuild - we use the same values for --verbosity across the CLI, but that value is interpreted different ways.

So ideally we'd have two (at least?) descriptions/snippets for verbosity that could be shared:

  • verbosity for msbuild-using commands
  • verbosity for non-msbuild-using commands

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@baronfel can you help me out by confirming which CLI commands use MSBuild. I believe it's:

  • build
  • clean
  • pack
  • publish
  • restore
  • test


Sets the verbosity level of the command. Allowed values are `q[uiet]`, `m[inimal]`, `n[ormal]`, `d[etailed]`, and `diag[nostic]`. The default is `minimal`. By default, MSBuild displays warnings and errors at all verbosity levels. To exclude warnings, use `/property:WarningLevel=0`. For more information, see <xref:Microsoft.Build.Framework.LoggerVerbosity> and [WarningLevel](../../csharp/language-reference/compiler-options/errors-warnings.md#warninglevel).
Sets the verbosity level of the command. Allowed values are `q[uiet]`, `m[inimal]`, `n[ormal]`, `d[etailed]`, and `diag[nostic]`. The default is `minimal`. By default, MSBuild displays warnings and errors at all verbosity levels. To exclude warnings, use `/property:WarningLevel=0`. Terminal logger (see --tl), which is the default in interactive sessions from .NET 9, shows limited output at all verbosity levels. For more information, see <xref:Microsoft.Build.Framework.LoggerVerbosity> and [WarningLevel](../../csharp/language-reference/compiler-options/errors-warnings.md#warninglevel).

- **`--use-current-runtime, --ucr [true|false]`**

Expand Down
Loading