Comments
2 comments
-
Reflector Pro executes some commands in the Command Window whenever a breakpoint is hit, until the point at which it has confirmed that the right assemblies and pdb files have been loaded for items that you have checked in the assemblies to decompile dialog. It does this to help diagnose problems when the wrong pdb file is loaded or a different assembly is loaded from those you chose to decompile.
This does mean that if you have selected some assemblies that your application doesn't use in the decompilation dialog, the commands are going to get executed on every breakpoint (as the code will keep trying to verify that they have been loaded correctly).
We could perhaps allow the user to turn off the checks. I've logged an enhancement request RP-723 -
Good! It's kinda irrelevent to me what it's doing. All I know is that when I'm working from home, I need to disable the addin and restart visual studio when i'm debugging. (It's VERy annoying).
Can't you use the Visual Studio API's to issue commands without using the command window??
Thanks for the insight!
-Sean
Add comment
Please sign in to leave a comment.
Can this be fixed somehow? It's like the reflector addin is issuing debugger commands causing that window to appear every time I run to the next breakpoint.
Thanks!
-Sean