Skip to content
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

Top Known Issues #5736

Open
8 of 10 tasks
mikadumont opened this issue Jun 8, 2023 · 4 comments
Open
8 of 10 tasks

Top Known Issues #5736

mikadumont opened this issue Jun 8, 2023 · 4 comments

Comments

@mikadumont
Copy link
Contributor

mikadumont commented Jun 8, 2023

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:

@mikadumont mikadumont pinned this issue Jun 8, 2023
@mikadumont mikadumont unpinned this issue Jun 29, 2023
@mikadumont mikadumont pinned this issue Jul 5, 2023
@mikadumont mikadumont changed the title Feature backlog Top Known Issues Jul 31, 2023
@Santas
Copy link

Santas commented Aug 15, 2023

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

Screenshot 2023-08-15 at 2 04 36 PM

@blackshot
Copy link

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

@jtotht
Copy link

jtotht commented Nov 13, 2023

#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?

@arunchndr
Copy link
Member

Adding #7535 to the known issue on release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants