A simple but useful module which really helps with my productivity when I used previous versions of Visual Studio. I also use Netbeans and Eclipse, and I love this feature in those editors and use it constantly.
Hitting F12 for me is not as quick/natural for me, personally. Productivity Power Tools has similar functionality of allowing you to control+click to peek a definition in VS2015, but I like the behavior of going to the definition much better than peeking it.
I think it would be nice to extend this module (or PPT) so that you can define peek and go to definition as shortcuts and have them as for instance control+click for one and shift+click for the other one, and just allow you to choose which maps to which function.
... Or at least make it so that it is harder to hit. Any time I am coding quickly there is a bit of time-overlap during my clicks and my key presses.... so if I am move along quickly - particularly if I'm copying and pasting - it's about a 50/50 shot that this thing will pop up and stops me in my tracks.
It's very frustrating.
I've modified current VSIX package (just added VS2015 support).
You can download Go To Definition for Visual Studio 2015 here
Download, Unzip, Run GoToDefVS2015.vsix, restart Visual Studio and enjoy it.
I think this would be a very userful feature (at least for me): go to definition from XML comments like those:
/// A loader, that is responsible for retrieving XYZ from the database.
/// E.g: <see cref="MyLoaderClass"/>.
Sometimes I do want to promote to document rather than just peeking definition.
Please refer and reply to this discussion:
I used to use the "Go to definition" feature of pre-2012 versions of Visual Studio to navigate identifiers that came from build errors (which happens excessively often when something goes wrong while comipiling templates).
It is counter productive to have to copy/paste identifiers from the build output to a code window that does not deserve polluting, only to then use the addin.
Would it be possible to make this addin work in the context of any text window, like the build output?
It may be possible, but definitely not straightforward. The extension itself doesn't actually do the "Go to definition" logic, it just basically triggers a press of F12 (the GoToDefinition command). If F12 does work in the output window, then it's just a matter of getting the extension there and figuring out what to underline on ctrl+mouseover.