-
Notifications
You must be signed in to change notification settings - Fork 677
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Roslyn Analyzer works even though I disabled It #5998
Comments
This is a side effect of switching to the new roslyn based language server as a default in the latest version of the extension. For now as workaround you can either downgrade or set the This is an option we should consider in the new roslyn based language server as well |
I upgraded to the latest version and set |
Hmm that's definitely unexpected. Mind sharing your C# / Omnisharp logs from the output window when you have the 'dotnet.server.useOmnisharp' setting checked? |
from c# output from c# dev kit output |
Ah gotcha, thanks for the additional info. When the devkit extension is installed, the In order to use the |
Is there any chance to fix it ? |
Mine have the same behaviour, but from the C# output log it will stuck at |
I want to use the IntelliCode extension but it depends on the C# Dev Kit, which will enforce the use of Roslyn. But it's so broken that the language server can't even be started, which renders the whole C# thing unusable. I'm on openSUSE Tumbleweed with .NET 7. UPDATE: I somehow fixed it by disable and reenable the dev kit extension a few times. |
Really? Unexpected? Considering latest few releases this kind of stuff becomes rather greatly expected. "Oh, look, they released a new version of C# extension! LET'S SEE WHAT DID THEY FUCK UP THIS TIME, SHALL WE?" |
Related to dotnet#5998 This ensures that the Background analysis scope option becomes the source of truth for both C# extension and OmniSharp
I don't like analyzing my code while Editing So I Disabled the Roslyn Analyzer through
Enable support for roslyn analyzers, code fixes and rulesets
settingBut It still works even after restarting language server and restarting vscode
I switched to version v1.26.0 and Everything is working fine
The text was updated successfully, but these errors were encountered: