Top Known Issues

[mikadumont]

In version 2.0, we made the new Roslyn language server the default option. However, we acknowledge that this version doesn't yet offer all the features of the previous OmniSharp version. If you require one of the following top known missing features, you can switch back to OmniSharp by following these instructions. Rest assured we are actively working to address these top known missing features in the C# extension which will target one of the upcoming releases:

• Diagnostics related feature requests and improvements #5951
• [O# Parity] Nested code actions including FixAll support for code fixes and refactorings #5735
• [O# Parity] Nuget restore #5725
• [O# Parity] Support loading non-solution based projects/files #5722
• [O# Parity] Project loading support for projects running on Mono #5721
• [O# Parity] Run and debug tests in context #5719
• Debug from .csproj and .sln #5876
• ProcessFrameworkReferences task failed unexpectedly (was: Pre-Release version not working but Release version is working) #5980
• language server cannot start unless the project is a sln #5923
• Any FixAll CodeFix does not work anymore. #7535

[theFish2171]

I just discovered I can get back to OmniSharp by myself about an hour ago.
This new extension is not yet ready for production.

Intellisense doesn't work (Specially in referenced projects)
Code refactoring doesn't work
Code navigation (F12 key) doesn't work (Properly).
Errors don't go away, even when fixed, until compilation
Debugger doesn't work (It is now shipped in a different extension)

Switching back to OmniSharp fixed all the problems.

[Santas]

@mikadumont What is the plan with the most upvoted issue? #490

[blackshot]

i would like to mention that #4580 is making C# Dev Kit completely useless for Blazor developing.

[jtotht]

#5787 is a major regression: if I’m interested in the return type of some library method, I can’t Ctrl+click on the method name and then Ctrl+click on the return type in the method signature. I personally consider it a blocker to upgrading to 2.x. I wish it was fixed ASAP, but if it doesn’t fit in your schedule, could you please at least list it here?

[arkalyanms]

Adding #7535 to the known issue on release.