-
Notifications
You must be signed in to change notification settings - Fork 684
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
Cannot "Go to definition" inside a definition #6021
Comments
Use v1.26.0. There is a bug on version 2 |
Likely related to #5787 |
Please try to disable the C# dev kit and intellicode for C# dev kit |
Had the same issue, reverting to 1.26.0 worked for me. For anyone that isnt aware... you can set a specific version of an extension by clicking the gear icon in the extension list and clicking "install another version..." |
Closing as duplicate of #5787 - once that issue is resolved various language features (incl go to definition) should work better in decompiled / metadata files. |
It's late, but I'm sure someone out there is struggling with this. Anyway, what worked for me and could work for you as well was installing an older version of the C# Dev Kit. Both the C# extension and the C# Dev Kit support 'Go to Definition,' and when you try to use the C# OmniSharp server, it won’t use the C# Dev Kit by default. The solution is to install a version of the C# Dev Kit that doesn’t conflict with other extensions. I guess they’ve been working on it, so it should be fixed soon. |
Steps to reproduce
Expected behavior
Should be able to go arbitrary deep into definitions. This works as soon as Omnisharp is enabled again.
Actual behavior
Doesn't do anything.
Additional context
Tried both with and withoug C# Dev Kit installed.
The text was updated successfully, but these errors were encountered: