Top Known Issues
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:
- [ ] https://github.com/dotnet/vscode-csharp/issues/5951
- [x] https://github.com/dotnet/vscode-csharp/issues/5735
- [x] https://github.com/dotnet/vscode-csharp/issues/5725
- [x] https://github.com/dotnet/vscode-csharp/issues/5722
- [x] https://github.com/dotnet/vscode-csharp/issues/5721
- [x] https://github.com/dotnet/vscode-csharp/issues/5719
- [ ] https://github.com/dotnet/vscode-csharp/issues/5876
- [x] https://github.com/dotnet/vscode-csharp/issues/5980
- [x] https://github.com/dotnet/vscode-csharp/issues/5923
- [x] https://github.com/dotnet/vscode-csharp/issues/7535
@mikadumont What is the plan with the most upvoted issue? https://github.com/dotnet/vscode-csharp/issues/490
i would like to mention that #4580 is making C# Dev Kit completely useless for Blazor developing.
#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?
Adding https://github.com/dotnet/vscode-csharp/issues/7535 to the known issue on release.