question-mark
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.

Verbosity not working

See original GitHub issue

Steps to reproduce

dotnet build MyProject.sln /v:d

Expected behavior

Display detailed logs

Actual behavior

Displays the detailed logs, but non descriptive warnings. For example:

 C:\Program Files\dotnet\sdk\1.0.1\Microsoft.Common.CurrentVersion.targets(1964,5): warning MSB3277: Found conflicts between different versions of the same dependent assembly that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed. [C:\Projects\MyProject\MyProject.csproj]

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.1)

Product Information:
 Version:            1.0.1
 Commit SHA-1 hash:  005db40cd1

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\1.0.1

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
vcsjonescommented, Apr 8, 2017

Workaround:

dotnet restore /ConsoleLoggerParameters:Verbosity=<your verbosity level>

0reactions
livarcocccommented, May 11, 2017

This is working on the latest 2.0 tooling.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Verbosity option is not working in GridSearchCV (Jupyter ...
Describe the bug​​ The problem is that GridSearchCV doesn't show the elapsed time periodically, or any log, I am set n_jobs = -1...
Read more >
python - unittest: increase module's verbosity when tested
I have a module mymodule that I test with unittest . The module logs to stdout diagnostics messages when is in verbose mode...
Read more >
Enable verbose startup, shutdown, logon, and logoff status ...
Verbose status messages may be helpful when you're troubleshooting slow startup, shutdown, logon, or logoff behavior.
Read more >
Annoying output window verbosity - Developer Community
When setting the Output Window verbosity to quiet, additional compiler error and warning details (notes, usually) are also hidden.
Read more >
Write-Verbose (Microsoft.PowerShell.Utility)
These commands use the Write-Verbose cmdlet to display a status message. By default, the message is not displayed. The first command assigns a...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found