Joey Robichaud

@esklarski Can you try the `mono-complete` package? > I did some checking and as far as I can tell msbuild is installed properly on my system. Mono does not use...

@esklarski Lets continue this investigation on https://github.com/OmniSharp/omnisharp-vscode/issues/5232. Hopefully we can come up with a workable solution.

@1w1f You can set the `omnisharp.sdkVersion` to the version string you would like to load. You can also configure your omnisharp.json like so ([see SDKOptions.cs](https://github.com/OmniSharp/omnisharp-roslyn/blob/d086e5bfb634427a82978ff6eed7522938012f8d/src/OmniSharp.Host/MSBuild/Discovery/Providers/SdkOptions.cs#L5-L14)). ```json { "SDK": { "Version":...

@davidwengier Is issue this on the Roslyn side or the debugger side?

@iSazonov Sorry you are running into issues with Generators. Can you share your full OmniSharp log from the Output pane?

@quassnoi The SourceTest.cs file is being opened as a transient file in the miscellaneous workspace. You would see the following in your log if the LogLevel was set to trace:...

@CapClumsy I think this may depend on which theme you are using. Using the included Visual Studio 2019 Dark theme I see

The C# extension now requires an installed .NET 6 SDK. The .NET 6 SDK can build projects that target `net5.0`. Be aware that the .NET 5 SDK is no longer...

@jcoble If you set the Omnisharp LogLevel to `trace` in VS Code Settings, are there additional details logged to the OmniSharp Log?

@harry-patel-jisc The error you are seeing typically occurs when you have an x64 build of the .NET SDK installed instead of arm64. To use 1.25.0 you should uninstall your x64...