[C# editor] Shift-F12 is listed in the context menu as "find all references" and is bound that way globally, but Shift+F12 is overridden @ Text Editor to Edit.GoToReference - by James M Manning

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 532624 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 2/10/2010 12:27:28 PM
Access Restriction Public


according to Tools -> Options -> Keyboard, I had Shift-F12 bound globally to Edit.FindAllReferences and at the Text Editor scope to Edit.GoToReference.  The context menu in the C# editor listed Shift-F12 next to "Find All References", but when invoked it (of course) resulted in Edit.GoToReference.

The context menu should not have listed the Shift-F12 keyboard accelerator for Find All References since its bound accelerator was overridden in a 'lower' scope.
Sign in to post a comment.
Posted by Microsoft on 3/20/2010 at 8:55 PM
Thanks for the feedback. It's been awhile since our last communication so I'm going to resolve and close this issue. If you're still experiencing problems, please reactivate or create a new Connect bug.

Weston Hutchins
Program Manager - VS Platform
Posted by Microsoft on 3/14/2010 at 1:01 PM

I'm just picking up this issue from Suzanne. This is the response from one of our developers:

"Attached profile has been customized and this behavior is not unexpected or in error. As you can see in the key bindings (attached), Shift+F12 is bound to Edit.GoToReference, F12 is bound to Edit.GoToDefinition in C# edit context. Only if Edit.GoToReference is un-registered, it would fall back to Edit.FindAllReferences."

It seems that the keybinding have been customized. If resetting your profile does, in fact, fix this issue, then we at least know there's a workaround. Were you importing a previous settings file when installing VS 2010?

Can you double confirm that everything is working as expected?

Weston Hutchins
Program Manager - VS Platform
Posted by James M Manning on 2/11/2010 at 5:32 AM
slightly changed the title/description based on the recent investigation.
Posted by James M Manning on 2/11/2010 at 5:27 AM
the exported settings file helps show what's going on, as 1) Edit.FindAllReferences isn't listed in the file (even though the Tools -> Options -> Keyboard says it's bound globally to Shift-F12 and 2) Shift+F12 is listed as Edit.GoToReference in the Text Editor scope.

If I reset all my settings back to C# defaults from the import/export dialog, FindAllReferences gets bound back to control+K, R and works fine.

It appears that Shift+F12 was bound to Edit.FindAllReferences globally (must be the default since it doesn't end up in the exported settings file) and Edit.GoToReference in the "Text Editor" scope. Because of the latter, it should not have been listed as the accelerator for Find All References in the C# editor context menu since it was overridden in the text editor scope.
Posted by James M Manning on 2/11/2010 at 5:01 AM
adding the exported settings
Posted by James M Manning on 2/11/2010 at 4:58 AM
adding the PSR that 'proves' I'm hitting Shift-F12 (since that's what PSR records)
Posted by Microsoft on 2/10/2010 at 7:18 PM
Thanks for reporting this issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Please export environment settings file by clicking Tools-> Import and Export Settings, after that, please send it to us so that we can conduct further.

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.

Visual Studio Product Team
Posted by Microsoft on 2/10/2010 at 7:04 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)