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.

"Warnings were encountered while loading the workspace" But No Warnings Shown in -v diag?

See original GitHub issue

Attempting to use this tool over an open source project I have (ManipulativeReplacer) throws this warning:

Warnings were encountered while loading the workspace. Set the verbosity option to the 'diagnostic' level to log warnings.

However running this in diagnostic verbosity -v diag shows no warnings in loading the workspace, Is this a bug?

*EDIT: Forgot to mention the version:

C:\GitHub\ManipulativeReplacer>dotnet format --version
5.0.142902+8012f4ede1bb9a4e90ac01efd204b0f1ee428f10

Complete output:

C:\GitHub\ManipulativeReplacer>dotnet format ManipulativeReplacer.sln --fix-style warn
  Formatting code files in workspace 'C:\GitHub\ManipulativeReplacer\ManipulativeReplacer.sln'.
  Warnings were encountered while loading the workspace. Set the verbosity option to the 'diagnostic' level to log warnings.
  Format complete in 4108ms.

C:\GitHub\ManipulativeReplacer>dotnet format ManipulativeReplacer.sln --fix-style warn -v diag
  The dotnet runtime version is '3.1.7'.
  The dotnet CLI version is '3.1.401'.
  Using MSBuild.exe located in 'C:\Program Files\dotnet\sdk\3.1.401\'.
  Formatting code files in workspace 'C:\GitHub\ManipulativeReplacer\ManipulativeReplacer.sln'.
  Loading workspace.
  Complete in 1768ms.
  Determining formattable files.
  Complete in 391ms.
  Running formatters.
  Running Code Style analysis.
  Determining diagnostics...
  Running 6 analyzers on ManipulativeReplacer.
  Complete in 1343ms.
  Fixing diagnostics...
  Complete in 6ms.
  Analysis complete in 1349ms.
  Complete in 1760ms.
  Formatted 0 of 11 files.
  Format complete in 3923ms.

Issue Analytics

State:
Created 3 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

3reactions

OtgonjargalKhcommented, Feb 9, 2022

how to fix this error during c# code linting through dotnet format in command line when new project created with win ui 3 ? “Warnings were encountered while loading the workspace. Set the verbosity option to the ‘diagnostic’ level to log warnings.”

1reaction

JoeRobichcommented, Oct 19, 2020

Should be fixed in https://dev.azure.com/dnceng/public/_packaging?_a=package&feed=dotnet-tools&package=dotnet-format&protocolType=NuGet&version=5.0.151904&view=overview

Top Results From Across the Web

vs code Problems with C# extension, Some projects have ...

Host Omnisharp server running using Stdio at location '/Users/zeyad/Documents/Sandbox/CSharpTut' on host 1365. [info]: OmniSharp.MSBuild.

Errors and warnings pane very unreliable.

I've seen numerous reports on the errors and warnings panes, all seem to get closed, but I still see the issue. If I...

dotnet format command - .NET CLI

The dotnet format command formats code to match EditorConfig settings for the current directory.

View Diagnostics - MATLAB & Simulink

You can view and diagnose errors and warnings generated by your model using the Diagnostic Viewer. The Diagnostic Viewer displays three types of...

Xcode 14 Release Notes

Xcode no longer builds bitcode by default and generates a warning message if a project explicitly enables bitcode: “Building with bitcode is deprecated....