|
I have the VSPro license and am running Visual Studio 2010. After upgrading to Reflector 7.4.0.178, Reflector.exe no longer runs when I right-click on a .NET symbol and choose "Open in .NET Reflector". When I do that, I can see the decompiled code show up briefly in my editor, but then the Reflector UI never appears. I think I may have inadvertently installed the upgrade with an instance of Visual Studio still running, so I don't know if that contributed to this problem. I tried upgrading again to Reflector 7.4.1.179 with no Visual Studio instances running, but the problem still exists. Any thoughts? |
|
Hi Guys, Thanks for reporting this issue again. We know this feature is working fine for the vast majority of users (via our feature usage reporting data) but you'll be pleased to know that as a result of your posts, and some more discussion today, we are going to try and get to the bottom of this in a future sprint. The following bug number is pretty useless to you but it will help us reference this post in the future once we have an update: RP-1937 If you don't hear anything more from us here it means we haven't yet prioritized this issue over other bugs and enhancements we are working on. Thanks again for taking the time to flag this for us. We really appreciate it. Greg Thanks! :)
(Oct 19 '11 at 07:09)
cremor
|
|
I have the exact same problem, although it was a bit different in older versions. The problem is that the Add-In creates a wrong command line argument for the Reflector UI. For more details see here. I didn't notice the change in behaviour earlier because I'm not using the Add-In anymore. You could try to disable the VS integration in the Reflector options and then enable it again, but most likely this won't change anything. |
|
Thanks for reporting this. It is now fixed (in 7.5.0.80) which will become available as an EAP at some point. I just tried EAP 7.5.0.90. The UI is starting again, but sadly still with the buggy command line args (http://forums.reflector.net/questions/247/open-in-net-reflector-not-jumping-to-typemember).
(Nov 02 '11 at 07:57)
cremor
You're getting an extra "%20{" pasted into the generated command line?
(Nov 02 '11 at 08:13)
Clive ♦♦
Yes, that "%20{" is still there with EAP 7.5.0.90.
(Nov 02 '11 at 10:18)
cremor
|
Have you managed to open Reflector.exe again yet?
No, I'm still seeing the problem - the Reflector.exe process never appears to be invoked.
I just downloaded and installed 7.5.0.90, and the UI now runs when I choose "Open in .NET Reflector". Thanks!