Source link navigates to the wrong symbol #81111
Description
This issue has been moved from a ticket on Developer Community.
Original Comments
Feedback Bot on 1/23/2025, 06:16 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Anonymized GDPR on 1/23/2025, 06:59 PM:
Hi, the feature “Enable Source Link support” Under Dubugging–> General is particularly useful when debugging. So if you don’t want to define to Source Link, you can disable the feature “Enable navigation to Source Link and Embedded sources” under Text Editor–>C#–>Advanced.
Can you please try and let us know if it works, thanks.
Yurui Chen on 1/23/2025, 10:33 PM:
If disabling these features does indeed restore normal operation, but sometimes I also need to view the source code of BCL through Source Link
Anonymized GDPR on 2/19/2025, 00:35 AM:
I can reproduce this issue and this issue has been escalated for further investigation, if there is any process, I will inform you immediately.
Feedback Bot on 5/6/2025, 10:28 PM:
We detected that this issue hasn’t received a lot of activity, votes, or comments in the past 90 days. Based on this, the issues severity and affected area, it’s my experience that this issue is unlikely to get fixed. To improve the situation, consider following best practices for quality problem reports, and giving us more details on how this issue is impacting you.
Eivind Dale on 9/29/2025, 03:30 PM:
Happens to me too; to get the correct symbol I must turn off Options > Text Editor > C# > Advanced > “Enable navigation to Source Link and Embedded sources”
This is after a total uninstall and re-install of Visual Studio 2022, the issue persists.
Todd Grunke [MSFT] on 9/29/2025, 04:22 PM:
Feedback Bot on 9/29/2025, 06:55 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Feedback Bot on 11/7/2025, 04:15 AM:
This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.