Comments
1 comment
-
> It appears to me that reflector pro is linking it's decompiled source
> with the original dll - so things work for viewing at runtime, is
> that correct?
Yes. We generate the source in a Reflector Pro folder and generate a pdb which links the original assembly to this generated source. We then put the pdb somewhere that Visual Studio will load it. Visual Studio will then display the generated source when you break inside the original assembly.
There is no edit-and-continue for this source code, so you cannot fix bugs by editing the source that is displayed.
Add comment
Please sign in to leave a comment.
Why I ask is I've used reflector pro and found the bug in the dll, but since the reflector decompiled code won't compile I guess there's no way to fix it? It seems if I make changes in Reflector Pro view of the code at runtime I can't get the new code to compile - it actually just throws off where it should be showing I am.
Do I understand this correctly or is there a way I can actually fix the bug in this dll - is reflector pro actually able to compile the code I can't from reflector?