Menu
This is driving me crazy. Ever since I installed ReSharper 4, F12 no longer seems to work. If you look at the all the ReSharper short cuts in the Goto sub menu Declaration doesn't have any assigned!
The only way I can go to declaration is by using Alt and ` and then selecting Declaration.
I have tried un-installing and re-installing ReSharper with no luck, I have also, in ReSharper option asked it to use the default Visual Studio Key Bindings but that doesn't to work either.
Interestingly, when I do use Alt and ` I actually get two entries for the Declaration option.
Has anyone come across this problem?
I am using Visual Studio 2005 SP1.
765
Go to Tools -> Options -> Keyboard, Reset all settings. Restart your visual studio and then try to use F12.
On the menu bar, choose Tools > Options. Expand Environment, and then choose Keyboard. Optional: Filter the list of commands by entering all or part of the name of the command, without spaces, in the Show commands containing box. In the list, choose the command to which you want to assign a keyboard shortcut.
Be sure your keyboard has its function key setting of the keyboard itself to send the F12 function to Visual Studio. It is an easy thing to miss. I had just installed Pulover’s Macro Creator and F12 was set as the global hotkey to pause a macro. It was intercepting the keypress before it had a chance to get to VS.
Sometimes it has noting to do with Visual Studio at all. Be sure your keyboard has its function key setting of the keyboard itself to send the F12 function to Visual Studio. It is an easy thing to miss. I had just installed Pulover’s Macro Creator and F12 was set as the global hotkey to pause a macro.
F12 also doesn't seem to work. I've tested this in Dart and Java. A colleague has experienced the same thing on OSX but seems to work fine on Windows 10 (both when upgrading from 1.12 -> 1.13)
Change Shortcuts for selected command to F12 (Text Editor), click Remove and OK. After this it works! I'd say THIS is the fix. After selecting to use the VS command instead of Resharper the first time you use F12, you would believe F12 would be used as "normal", but resharper STILL maps F12 to its own use.
I ran into the same issue and resolved it by first resetting my Visual Studio keyboard mappings:
Tools > Options > Keyboard > Reset
Then going into the ReSharper options and applying the scheme:
Resharper > Options > Visual Studio Integration > Apply Scheme
Update:
For VS2017 onwards:
Tools > Options > Environment > Keyboard > Reset
For Resharper 2017.2:
Resharper > Options > Environment > Keyboard & Menus > Keyboard Shortcuts > Apply Scheme
133
I have had a few occasions where Resharper and Visual Studio keybindings got mixed up and I had problems sorting them out.
If it is only one or two bindings you care about then you can change them by going to the
Tools->Customize->Keyboard menu option.
25
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
