Comments
Sort by recent activity
Sorry, but we don't have a solution to this. / comments
Sorry, but we don't have a solution to this.
> 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. / comments
> 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 Reflecto...
The fix I made was to handle the special path components when an assembly is decompiled using Reflector Pro. I didn't make an equivalent fix on the code path that deals with the "Export" functionality in Reflector.
Currently, the best workaround is probably to decompile the assembly using Reflector Pro and then generate a project file yourself. / comments
The fix I made was to handle the special path components when an assembly is decompiled using Reflector Pro. I didn't make an equivalent fix on the code path that deals with the "Export" functional...
The link used to point to the EAP (early access version) of Reflector 6.5. That version has now been released - you can get it by using Help/Check For Updates on your existing version of Reflector, or by downloading the latest version from the Red Gate site. / comments
The link used to point to the EAP (early access version) of Reflector 6.5. That version has now been released - you can get it by using Help/Check For Updates on your existing version of Reflector,...
Hi.
Thanks for reporting that. I don't know of any workaround, but on Monday I'll have a look at putting a fix into the next EAP of Reflector 6.5.
Clive / comments
Hi.
Thanks for reporting that. I don't know of any workaround, but on Monday I'll have a look at putting a fix into the next EAP of Reflector 6.5.
Clive
I put a fix into the Reflector 6.5.0.123 EAP which you can download from the EAP forum. http://www.red-gate.com/messageboard/vi ... .php?f=117 / comments
I put a fix into the Reflector 6.5.0.123 EAP which you can download from the EAP forum.http://www.red-gate.com/messageboard/vi ... .php?f=117
You are looking at C# 3.5 code with some property definitions of the form:
int Foo { get; set; }
If you decompile with the settings as 2.0, you see the compiler generated code. [CompilerGenerated]
private int <Foo>k__BackingField;
private int Foo { [CompilerGenerated] get; [CompilerGenerated] set; }
If you decompile at 3.5 then the compiler generated items are hidden, giving just the code private int Foo { get; set; }
You can change the optimization level in View/Options/Optimization. / comments
You are looking at C# 3.5 code with some property definitions of the form:
int Foo { get; set; }
If you decompile with the settings as 2.0, you see the compiler generated code.[Co...
Hi.
The object browser only supports public types, so you need to find the decompiled source file for the private or internal type in order to set a breakpoint. A trick for doing this is to go to the decompiled definition of one of the public types, and then file/open/file in the code view of that type will let you open the source file corresponding to one of these internal types. / comments
Hi.
The object browser only supports public types, so you need to find the decompiled source file for the private or internal type in order to set a breakpoint. A trick for doing this is to go to t...
Hi.
You are probably trying to decompile the reference assembly instead of the real assembly. Microsoft supplies a set of reference assemblies that contain the metadata but no IL instructions. This gives the effect you are seeing.
You need to use the real assembly. The easiest way to find it is via "File/Open Cache". / comments
Hi.
You are probably trying to decompile the reference assembly instead of the real assembly. Microsoft supplies a set of reference assemblies that contain the metadata but no IL instructions. This...
Thanks for reporting these.
The first is already in our bug tracking system.
Do you have a reproducible case for the second. It doesn't happen in some small test examples I have written - I get this.M_strNodeName.Length. / comments
Thanks for reporting these.
The first is already in our bug tracking system.
Do you have a reproducible case for the second. It doesn't happen in some small test examples I have written - I get thi...