search

madskristensen / Tweakster

A Visual Studio extension
Apache License 2.0
240 stars 23 forks source link

Verbosity level selection on Output Window does not fully change build verbosity #59

Open djohnst10 opened 3 years ago

djohnst10 commented 3 years ago

The Verbosity level selection on the Output Window is a nice enhancement but I'm finding that it doesn't work completely.

I've found that the Verbosity setting in the Options dialog does reflect what the Verbosity setting on the Output Windows says and vice versa. However, the only way to reliably change the build output verbosity level is to change it in the Options dialog.

Using the Verbosity level selection on the Output Window to change the verbosity from Minimal to Diagnostic produced far less output than expected. This happens both ways: if I have the level at Diagnostic and the build produces diagnostic-level output, using the Output Windows's Verbosity level selector to change the verbosity selection to Minimal does not obviously reduce the amount of output.

While the amount of output with the Verbosity level selection on the Output Window set to Diagnostic is not what is expected, it is still different from Minimal, the previous setting. The output includes some extra messages that appear to be from NuGet of the form:

"Failed to resolve all items referenced by '{project path}'. This message can typically be ignored. The issue may be resolved by fully restoring and building the solution. If the unresolved item is a project reference this can lead to an incomplete NuGet restore result and missing package references. To ensure that restore is able to find all projects verify that all projects are referenced correctly and exist on disk."

The project types I'm building are .NET Framework projects and ASP.NET projects. None are the newer SDK-style of project.

ArchieCoder commented 3 years ago

I filled this bug in VS database: https://developercommunity.visualstudio.com/t/quiet-output-verbosity-inaccurate/1390279

What Srdjan Jovčić [MSFT] said is right, the Tweak tool has the bug. I did the test disabling the tool and the verbosity is set correctly.

dh0well commented 2 years ago

This bug hit me recently too. I set the verbosity to Diagnostic in order to determine why a project was unnecessarily building all the time and none of the "project not up to date" messages were appearing. Took me a while to figure out it was this extension affecting the diagnostic messages. Regrettably, I may have to disable/uninstall this extension, I don't really trust what else may be getting filtered out.

Note: Tweaks 2022 does the same thing in my VS22 install.

StevenBonePgh commented 2 years ago

@dh0well for your issue in determining why the project is being built, I raised an issue/PR for #60 See this comment for the source of the change. I think it is easier to use that tweak to elevate only the up to date check verbosity rather than changing the overall msbuild verbosity. You may need to restart VS after changing it for it to take effect.