-
Notifications
You must be signed in to change notification settings - Fork 676
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
Go To Definition should use source link or embedded source (pdb) instead of metadata-as-source when available #2207
Comments
FWIW, we'll want this in Visual Studio as well and there might be some movement on making that work at some point (VS has go to disassembly now too!). I think the best way to go about this would be to implement the feature in Roslyn, expose a properly Go to Definition API and make OmniSharp use it. @jinujoseph: Are we tracking Source Link or embedded PDB sources for Go to Definition in Roslyn somewhere? |
Closing in favor of dotnet/roslyn#26366 |
yes actually here dotnet/roslyn#24349 |
Thanks! |
Half of year has gone. Hoping for this feature! |
Greetings gentlemen and thank you for the wonderful extension. |
Environment data
VS Code version:
Version 1.22.2 (1.22.2)
C# Extension version:
1.15.0-beta4
Steps to reproduce
Use "Go To Definition" from command-pallete, context menu, keyboard shortcut, or CMD/CTRL+CLICK on a symbol contained within a package reference that contains portable-pdb embedded source or sourcelink metadata (unauthenticated).
Expected behavior
Referenced source is rendered 👍
Actual behavior
Metadata-as-code is rendered 👎
I used
dotnet-sourcelink
to verify that the sourcelink urls are available as well as to test a nupkg containing a portable pdb with embedded source.The text was updated successfully, but these errors were encountered: