Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
dotnet run by default, is too verbose - Use --verbosity instead
See original GitHub issueBy default, a simple dotnet run should just run. No details at all.
Perhaps there’s a -v1 or -v2? Basically verbose is great, but run should just run. THIS is not needed:
C:\Users\Scott\Desktop\foo>dotnet run
Project foo (.NETCoreApp,Version=v1.0) was previously compiled. Skipping compilation.
Hello World!
So:
| command | output |
|---|---|
| run | no output |
| run -v | current verbose output |
| run - (need suggestions here) | The current run behavior, basically “info level” output |
Issue Analytics
- State:
- Created 7 years ago
- Reactions:13
- Comments:19 (5 by maintainers)
Top Results From Across the Web
ASP.NET Core logging too verbose
When you set Debug , it will log Critical, Error, Warning, Information, Debug levels. It will not log Trace (highest verbosity).
Read more >dotnet run command - .NET CLI
The dotnet run command provides a convenient option to run your application from the source code.
Read more >dotnet build command - .NET CLI
Running dotnet build is equivalent to running dotnet msbuild -restore ; however, the default verbosity of the output is different.
Read more >dotnet restore command - .NET CLI
Learn how to restore dependencies and project-specific tools with the dotnet restore command.
Read more >dotnet test command - .NET CLI
The default is minimal . For more information, see LoggerVerbosity. args. Specifies extra arguments to pass to the adapter. Use a space to ......
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
@plioi I would agree, as long as the default verbosity is lowered. I don’t need to see
Project foo (.NETCoreApp,Version=v1.0) was previously compiled. Skipping compilation.everytime, if ever.@blackdwarf What’s the latest tooling exactly? I just downloaded dotnet-dev-osx-x64.1.0.0-preview2-1-003177.pkg a few seconds ago and it still has this issue.