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.
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.
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
For ReSharper 8 and Visual Studio 2012:
Tools > Options > Keyboard > Reset
Then going into the ReSharper options and applying the scheme:
Resharper > Options > Environment > Keyboard & Menus > (Select Visual Studio under Keyboard Shortcuts) > Apply Scheme > Save
I had this problem and it was resolved by following the steps described in the picture:
Open Visual Studio Tabs on the path: Tools>>Options>>Keyboard
Open Visual Studio Tabs on the path: Resharper>>Options>>Keyboard & Menus and Do the following:
And Then Reopen the path above and do the following:
Finally, close the Visual Studio and open it.
I had this issue in VS2015 using Resharper 9.1.3, I tried Ryan's answer but it still didn't work.
- After doing the steps Ryan outlined, I clicked F12 where Resharper asks What do you want to do?, I select Use Visual Studio commands. Still doesn't work.
- Tools > Options > Keyboard > Select ReSharper.ReSharper_GotoNextHighlight from command list box
- Change Shortcuts for selected command to F12 (Text Editor), click Remove and OK.
After this it works!
I had the same problem with VS2013 and Resharper 9. I have a code like this:
gridList.Method1();
gridList.Method2();
I then right-click on any of gridList and click Find Usages (or just use Shift+F12) but it says "Usages not found" even though it is just one line away! Sometimes VS restart would help, sometimes it wouldn't. It looks like clearing the cache of Reshaper helps though: Resharper -> Options -> Environment -> General -> Clear Caches. This needs VS to be restarted, but then it started working as expected.
It is possible that you have enabled Fn mode (Blue Keys) on your keyboard which overrides default behavior of functional keys including F12.
I ran into this problem after an organizational change that caused my windows profile to change. I tried the solutions listed above, but nothing seemed to work. Here is how I fixed it (brute force worked!)
NOTE: Steps listed are for VS 2012 and ReSharper 7.1.3
- Uninstalled Re-Sharper
- Exit visual studio, ensure the process devenv.exe is no longer there in the running processes (was there in my case and I had to do a "End Process Tree" from Task Manager)
- Fired up VS 2012, and from the menu Tools -> Options -> Environment -> Keyboard selected Visual C# 2005 (or any other setting you love) and pressed Reset
- Shutdown VS again (and ensure devenv.exe has been killed in Task manager)
- Re-installed re-sharper
Best of luck!
These steps solved it for me:
- Uninstall keyboard in Device Manager
- Re-insert your keyboard usb
"Web Essentials" Add or update visual studio "Web Essentials" You can find it at: Menu>>Tools>>Extensions and Updates
I hope this will save your time. It worked for me.
ReSharper added a crap 'good' new thing that they now call a feature: Smart Go To Declaration. As dumb as it may sound, it comes enabled by default: crap 'good'.
The feature is described on the link provided from here but honestly at least it should've keep it disabled, not reinvent the wheel. It also tells you how to disable that crap 'good' feature.
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. It was intercepting the keypress before it had a chance to get to VS.
Solution is to change that hotkey to something else. I chose Ctrl-F12. The input box is on the top right of the Pulover window.
来源：https://stackoverflow.com/questions/955193/f12-no-longer-works-in-visual-studio