Restore F12 (Go to Definition) for VS

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Topics:

vs2010 x23
integration x17

asked: Mar 30 '11 at 01:47 PM

Seen: 3350 times

Last Updated: Mar 30 '11 at 01:47 PM

Related Questions

Restore F12 (Go to Definition) for VS

How can I get the default handling for F12 back? Reflector is too slow so I do not want to use it all the time.

asked Mar 30 '11 at 01:47 PM kzak 93

Bart ♦♦ Mar 31 '11 at 10:51 AM

I've now added this as an enhancement request. Reference is RP-1313.

(comments are locked)

6 answers:

oldest newest voted first

It would be nice to have two commands - one for Reflector and another for the native behavior (metadata type definition for c#). Turning the addon on and off is not a viable solution.

This command blows up in VS 2008 and it is nice to have just the type def sometimes (actually it would be nice to have Metadata & Reflector & Object Browser linkage).

Additionally, the base types lose the f12 lookup ability in the reflector content.

This feature is a good idea but it definitely needs more attention.

The ability to decompile a single function DURING a debug session is awesome!

answered Mar 02 '12 at 05:22 PM

ReflectorFan
41 ● 2

Clive ♦♦ Mar 05 '12 at 08:19 AM

Thanks for the comments. The feature is available using its own accelerator, but there is currently no way to turn off the F12 override. I'll add an enhancement request to track this.

agaace Apr 07 '12 at 11:33 PM

+1. I want both and use them at the same time. The native metadata is faster AND it contains XML comments for classes/methods. For example, if I'm implementing an interface, I often open metadata for it, and copy + modify comments for my class, so my class has consistent comments with those in framework.

IPWright83 Sep 20 '12 at 09:07 AM

@Clive: Is there a way to track enhancements? I'm interested in knowing if this has been fixed or not?

Clive ♦♦ Oct 02 '12 at 01:57 PM

In the next EAP, the first for 7.7, which will probably go out tomorrow morning, this behaviour will be configurable using an item on the .NET Reflector menu.

fschwiet Oct 04 '12 at 07:31 PM

I had problems with the EAP. Uninstalling the reflector addin for now, this behavior has been bothering me for quite awhile but I always though resharper was the problem. This is probably the last time I'll buy reflector, given all I want from visual studio is a "open in reflector" button that opens whatever type I want in the reflector app itself. I do not want the decompiled code to open as a doc in visual studio.

(comments are locked)

Please count another vote for turning off the F12 override. In addition to reflector being slow sometimes, the more important for me issue is that standard Visual Studio's F12 shows help texts while reflector does not.

As for its own accelerator that you mention - if you mean the "Go to decompiled definition" context menu, I have installed developers bundle v7, and selecting that menu item does not do anything at all (while F12 works as discussed in this thread).

answered Mar 14 '12 at 02:13 PM

samid
31 ● 2

gabrielmaldi Aug 07 '12 at 05:49 PM

Same here, I added a new question for the matter: http://forums.reflector.net/questions/2589/go-to-definition-vs-go-to-decompiled-definition

And I'm definitely in favour of having both options available: one for going to the "normal" definition and one for the decompiled definition.

pjchristmas Oct 01 '12 at 03:17 PM

Agreed. Without this the add-in is not worth leaving installed.

(comments are locked)

I have VS2010 ultimate + reflector 7.6.0.808. If VS integration is installed, the F12 goes to the disassembled code while the reflector's "go to decompiled definition" context menu command doesn't do anything. This behavior is broken IMHO.

REDGATE: can you PLEASE FIX THIS? Or, if I'm doing something wrong please point me to it...

P.S.: because I need the original F12 functionality, I wanted to uninstall the Reflector Visual Studio integration. In previous version of the Reflector IIRC there was a menu command that allowed to relatively easily turn VS integration on or off. Now it's gone, and Reflector does not show up in VS' add-in manager, on my system anyway. So for the record, to uninstall VS integration this command line works:

vsixinstaller /u:04e215d3-4dfd-4ae4-b72c-d5ef91dc603b

answered Sep 11 '12 at 05:19 PM

dimas
11 ● 3

Clive ♦♦ Sep 12 '12 at 10:00 AM

It is no longer an add-in, but an extension - you can uninstall that using the tools/extension.... menu item.

(comments are locked)

I am really wondering that there are not much more people urging for a seperate reflector button and leaving the "go to definition" feature of VS that many of use use 100 times a day alive. This way the only way out is to disable relector for VS. Which causes doubts why one would by it at first.

answered Aug 29 '12 at 08:02 PM

citykid
1 ● 2

fschwiet Oct 04 '12 at 07:46 PM

I wasn't urging this as I thought resharper was causing the problem. This is pretty bad I'm with you on that.

(comments are locked)

You could turn turn off the reflector add-in in visual studio (tools - addin manager) when you're not using it.

answered Mar 30 '11 at 02:15 PM

ecodcode
215 ● 1 ● 8

(comments are locked)

I've upgraded to Reflector 8.0.1 and now I can see a check-box menu item "GoDefinition (F12)" in the Visual Studio's menu ".NET REFLECTOR". (It may have been there also in previous version - I don't remeber) After unchecking this option, the F12 really goes to metadata definition instead of going to decompiled code.

However, the "Go To Decompiled Definition (Shift+Alt+G)" context-menu item still does nothing. Am I doing something wrong or is RedGate ignoring this bug across major release?

answered Jan 25 at 03:34 PM

Jan Šotola
1 ● 2

ecodcode Jan 30 at 02:14 PM

It's pretty misleading, I've only ever gotten "Go to Decompiled Definition" to work when I've been inside decompiled code going to another piece of decompiled code. There doesn't seem to be a way at the moment to get both decompiled code and the metadata definition at the same time (other than by the .NET Reflector menu F12 toggle)...

(comments are locked)