Doesn't navigate to function definitions, it decompiles code instead #77435
Labels
Area-IDE
help wanted
The issue is "up for grabs" - add a comment if you are interested in working on it
Milestone
This issue has been moved from a ticket on Developer Community.
[severity:I'm unable to use this version] [regression] [worked-in:don't know by now]
The first thing I have used in the new version didn't work and I rolled back to the previous one. If I want to navigate to the function definition, instead of opening the function itself , opens a decompilation of the code. It didn't happen in the previous version and it's very anyoing , time consuming and inefficient. That's why I have decided to rollback to the previous version.
Original Comments
Feedback Bot on 3/2/2025, 10:25 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.
Yanghua Zhang[MSFT] on 3/2/2025, 11:08 PM:
Thanks for your feedback. Does this reproduce for all project or specific project? If it’s reproduced with the specific project, which project do you use (C#/C++ console, Web or others )? It would be very helpful if you could provide a sample solution or some screenshots that has this problem. We look forward to hearing from you. Thanks.
Why do we ask for more info?
We try to reproduce all issues reported with the information provided in the description and comments. When we can’t reproduce the issue, we ask you for more information so we can resolve the issue as quickly and efficiently as possible.
In our guidelines, you can get tips on how to provide clear and simple reproducible steps.
Xavier Matavacas on 3/3/2025, 00:15 AM:
(private comment, text removed)
Feedback Bot on 3/3/2025, 00:18 AM:
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 3/5/2025, 01:54 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.
The text was updated successfully, but these errors were encountered: