Skip to content
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 implementation broken (ctrl+f12) in VS 2022 17.12 #75974

Open
vsfeedback opened this issue Nov 19, 2024 · 0 comments
Open

Go to implementation broken (ctrl+f12) in VS 2022 17.12 #75974

vsfeedback opened this issue Nov 19, 2024 · 0 comments

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.


[severity:I'm unable to use this version] [regression] [worked-in:17.11]
Go to any class that inherits another one, press ctrl+f12 on it: it shows the references window instead of going into the implementation of the inherited class. Right click "go to implementation" shows the same behaviour. After re-setting the key-binding, it still shows the same behaviour.


Original Comments

Feedback Bot on 11/13/2024, 09:49 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.

Runtong Liu (Centific Technologies Inc) [MSFT] on 11/15/2024, 00:31 AM:

Thank you for taking the time to log this issue!
This may be by design. You can double click in the Find Symbol Results window and will going into the specify implementation of the inherited class. Details see https://learn.microsoft.com/en-us/visualstudio/ide/navigating-code?view=vs-2022#go-to-implementation.
If you still have questions, please describe in detail what results you expect and what the actual results are.

Wouter Paap on 11/15/2024, 00:50 AM:

I might be wrong, but this is not how I remember it. Ctrl+F12 now does exactly the same thing as Shift+F12. If you review the reproduction steps, you will also see the “Find All References” window opens on the left.
I understand we also have Ctrl+Home, which would show all the base-classes; but I would honestly expect Ctrl+F12 to step directly into the base-class itself, like it still does with other code: it goes directly into the implementation of the element I use Ctrl+F12 on.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-IDE untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 19, 2024
@arunchndr arunchndr added Go To Implementation Bug and removed untriaged Issues and PRs which have not yet been triaged by a lead labels Nov 26, 2024
@arunchndr arunchndr added this to the 17.14 P1 milestone Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants