Adding Ctrl-Click "Go To Definition" support to Visual Studio 2015

Question

Previously using Visual Studio 2013, I would use the awesome extension from Noah Richards which would add Ctrl-Click as a shortcut for Go To Definition, but he hasnt updated the extension to be compatible with VS2015. And as far as I know, VS2015 doesnt provide any way to have this functionality by default.

Solution 1

So here's how I fixed this.

1. First download Noah Richard's extension from: https://visualstudiogallery.msdn.microsoft.com/4b286b9c-4dd5-416b-b143-e31d36dc622b

2. Save the .vsix file somewhere on your computer

3. Open the file with Winzip / Winrar or similar (it's just a disguised .zip file so you could change the extension to .zip)
4. Open the extension.vsixmanifest file in a text editor
5. Add the following lines inside the <SupportedProducts>...</SupportedProducts> section:

<VisualStudio Version="14.0"> <Edition>Pro</Edition> </VisualStudio>

6. Update the zip file with the modified file and change it back to a .vsix file.
7. Double click the .vsix and install.

Solution 2

Install Productivity Power Tools 2015.

Comments

[MasterJoe]

I tried to install it using these instructions-stackoverflow.com/questions/25906944/…. Got an error that version is not supported. Looked at extension.vsixmanifest. It mentions only Pro versions of visual studio. I have 2012 express. What do I add to the manifest file to make it work ?

[Mikepote]

@testerjoe2 I'm guessing you can just use <Edition>Express</Edition> or something similar. You can also open another .vsix file to see what entries they have.

[rakslice]

Productivity Power Tools 2015's default configuration is for Ctrl-click to Peek Definition. If you want it to Go To Definition instead, go to Tools > Options > Productivity Power Tools > Other Extensions, and uncheck Ctrl Click shows definitions in Peek

[sparrowt]

It's been updated (Nov 2015) since this answer, and now claims to work with VS2015 without modification.

[Young Emil]

For the link you provided, they made a note which I think is necessary for us to know Note: This extension is only supported up to Visual Studio 2017....... .