1,102 questions
How to fix "Go To Definition" jumping into metadata in Visual Studio 2022
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 49%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWR%3C/text%3E%3C/svg%3E)
Wojciech Rajchel | reconline AG
0
Reputation points
Hi
I have a dll c# project. This project is referenced as a project from other .Net projects. The referenced project is added as existing project to a solution. The function Go To Definition always jumps into metadata of the dll project. I tried multiple hints, deleting .vs file, setting various options under Debug settings, clearing solution etc. The dll project has many classes. To test the issue I removed almost all classes and leaved only one class with one method. It worked and Go To Definition jumped correctly into actual code. Next I tried to delete classes with external references such as database dll references step by step to check what part of the code causes the issue. The codebase is large and I couldn't find what causes the issue.
Did you have the same or similar issue? I have found some posts from previous years and then the issue was submitted as a bug to Microsoft. I have the newest version of MS Visual Studio 2022.
Developer technologies | Visual Studio | Debugging
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 86%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
David Lowndes 2,640 Reputation points MVP2025-05-12T11:34:52.1+00:00 Do you have a link to the bug report?
If there's no satisfactory resolution to that bug report, all I can suggest is that you continue to try to pin down the cause of the issue and assuming you can find the cause, either add that information to the current bug report, or open a new one yourself with a solid repro.
Sign in to comment
Sign in to answer