.NET Reflector add-in incompatible with Resharper ?

Explore, browse and analyze .NET assemblies

Moderators: Luke Jefferson, Charles Brown, StephenC, Alex.Davies, Greg.Tillman, melvyn.harbour

.NET Reflector add-in incompatible with Resharper ?

Postby tom103 » Fri Jul 16, 2010 11:09 am

In the Visual Studio code editor, when I click on "Open in .NET Reflector" in the context menu, Resharper kicks in and shows me the declaration of the item (not its source), and the Reflector add-in displays this message :

The source code already exists for this item, so you do not need to use .NET Reflector


So, since I installed Resharper, I haven't been able to use Reflector in VS.

Not sure if the bug is because of Resharper or .NET Reflector...

EDIT: it is the same issue described in this topic. I didn't find it at first because it didn't mention the exact error message.
tom103
 
Posts: 8
Joined: Wed Jun 09, 2010 10:49 pm
Location: Paris, France

Postby Alex.Davies » Thu Jul 22, 2010 3:17 pm

It's not really either of our fault, I've been working with the guys at JetBrains. The trouble is that the only way it was feasible to add this feature in Reflector is by piggybacking on VS's go to definition (F12) feature. Without doing that, we would have to implement a complete parser for the language.

Of course R# does implement a parser, and extends the go to definition in ways the Reflector add-in can't deal with.

It usually works if you set R# to open the Object Browser when you press F12.
Alex
Developer,
Red Gate .NET Tools
Alex.Davies
 
Posts: 335
Joined: Tue Dec 02, 2008 12:23 pm
Location: Cambridge, uk

Postby tom103 » Sun Jul 25, 2010 6:29 pm

Alex, thanks for your reply.

Unfortunately, that's not what I want... I still want to see the definition when I press F12. I only want to open Reflector when I explicitly use the "Open in .NET Reflector" menu option
tom103
 
Posts: 8
Joined: Wed Jun 09, 2010 10:49 pm
Location: Paris, France

Any solutions on the horizon?

Postby dwhite » Sat Sep 18, 2010 8:06 pm

Are there any solutions for this? I love R# and Reflector Pro. I use F12 to go to the metadata. It does work against the Object Browser, but it ruins the work flow to have to navigate to the object browser just to bring up Reflector.

-Damien
dwhite
 
Posts: 1
Joined: Sat Sep 18, 2010 6:30 pm

Postby Clive Tong » Wed Sep 22, 2010 8:32 am

Sorry, but we don't have a solution to this.
Clive Tong
 
Posts: 283
Joined: Thu Dec 04, 2008 5:42 pm

Postby iluzyani » Thu Sep 23, 2010 11:10 am

Don't know if this is the same problem, but I use the following workaround:
Uncheck option "Enable navigation to external sources" at Resharper Options -> Tools -> External Sources
OR leave it enabled, but move "Object browser" item to top of the list. Works for me.
iluzyani
 
Posts: 2
Joined: Thu Sep 23, 2010 11:06 am

Postby Alex.Davies » Thu Sep 23, 2010 11:15 am

Yes, that's what I meant when I said:
"It usually works if you set R# to open the Object Browser when you press F12."

Thanks for the extra details how to do that, I'd forgotten.
Alex
Developer,
Red Gate .NET Tools
Alex.Davies
 
Posts: 335
Joined: Tue Dec 02, 2008 12:23 pm
Location: Cambridge, uk

Postby iluzyani » Tue Sep 28, 2010 2:44 pm

Sorry, didn't got it from your comment. Basically, I tried to answer to tom103's problem. And I don't have problems with F12 after setup, works as should.
iluzyani
 
Posts: 2
Joined: Thu Sep 23, 2010 11:06 am


Return to .Net Reflector 6.x and .NET Reflector 6.x Pro

Who is online

Users browsing this forum: No registered users and 0 guests