"dotnet build" should show build result and timing information at default verbosity level
See original GitHub issueMoved from https://github.com/dotnet/sdk/issues/483 filed by @DamianEdwards
It seems that dotnet build
is running at a quieter than normal/default MSBUILD verbosity level, meaning usual output like the build result and timing information (like below) isn’t shown:
I think it would be better to stick to the defaults or if possible tune the output to display the information we want for a great default CLI experience.
Comment by @rainersigwald
Note that this is independently controllable from overall verbosity via /consoleloggerparameters:Summary
.
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (11 by maintainers)
Top Results From Across the Web
"dotnet build" should show build result and timing ...
It seems that dotnet build is running at a quieter than normal/default MSBUILD verbosity level, meaning usual output like the build result ......
Read more >dotnet build command - .NET CLI
The default is minimal . By default, MSBuild displays warnings and errors at all verbosity levels. To exclude warnings, use /property: ...
Read more >dotnet clean command - .NET CLI
The default is normal . For more information, see LoggerVerbosity. Examples. Clean a default build of the project: .NET CLI
Read more >dotnet command - .NET CLI
The dotnet command has two functions: It provides commands for working with .NET projects. For example, dotnet build builds a project.
Read more >dotnet test command - .NET CLI
The dotnet test command builds the solution and runs a test host application for each test project in the solution. The test host...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just update the msbuild number in the CLI. The change is a subset of https://github.com/dotnet/cli/pull/5199.
This is not closed yet, the update of MSbuild was to unblock the fixing. I will send a PR today with the actual fix.