Comments
7 comments
-
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, 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 -
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 -
Sorry, but we don't have a solution to this.
-
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. -
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. -
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.
Add comment
Please sign in to leave a comment.
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.