Comments
Sort by recent activity
Thanks for reporting that.
I've made a fix which will be available in the next EAP. / comments
Thanks for reporting that.
I've made a fix which will be available in the next EAP.
Hi.
Thanks for the bug report. I think you're getting an exception in the code which locates the assemblies from the information that Visual Studio gives us about the references.
In the 6.1 version it was possible to get a Nullreference exception. This has been fixed in the recent EAPs (available at http://www.red-gate.com/messageboard/vi ... .php?f=117) to raise an exception which should tell you which item cannot be located.
To help us narrow this down, can you give us some information about the projects in your solution?
Thanks / comments
Hi.
Thanks for the bug report. I think you're getting an exception in the code which locates the assemblies from the information that Visual Studio gives us about the references.
In the 6.1 versio...
The code for resolving assemblies inside Reflector Pro looks for a referenced assembly next to the assembly being processed and also searches the GAC. There isn't any way to add search directories to this resolution though I'll log that as an enhancement.
Currently, I think the only work around is to copy the required assemblies, either manually or by setting a reference to them and setting "copy local" to get Visual Studio to do the copy for you. / comments
The code for resolving assemblies inside Reflector Pro looks for a referenced assembly next to the assembly being processed and also searches the GAC. There isn't any way to add search directories ...
There's currently no easy way to change back to a previously regenerated set of assemblies once you have done the undo. You have to go through the regeneration process again by selecting the original assemblies in the assembly chooser. / comments
There's currently no easy way to change back to a previously regenerated set of assemblies once you have done the undo. You have to go through the regeneration process again by selecting the origin...
When an assembly is compiled, a debugger signature may be stored into the assembly to allow the assembly to be matched against a pdb file. We need this ifnormation so that we can put it into any pdb file we generate to allow Visual Studio to match them.
It is possible to build assemblies without this debugger signature. For example, on the Advanced settings on the build tab of a C# project in Visual Studio, one can chose "Debug Info" as none, and various obfuscators also remove the header if it is present.
If the user choses to decompile such an assembly, we have no way to generate a pdb that Visual Studio will recognise as being connected to the assembly. We therefore regenerate the assembly - we add a debug signature and write the assembly to the directory that the user provides. We then offer the choice of fixing up the project to point to this newly generated assembly. We can then generate a pdb for the new assembly and it will be matched by the debugger because of this signature.
So, to answer your question, the dialog will only come up if you chose to decompile an assembly which doesn't have such a signature. / comments
When an assembly is compiled, a debugger signature may be stored into the assembly to allow the assembly to be matched against a pdb file. We need this ifnormation so that we can put it into any pd...
I think this is probably because you are looking at a "reference assembly" instead of the real framework assembly. Reference Assemblies, stored in C:\Program Files\Reference Assemblies, contain the metadata, but don't contain any of the IL instructions.
When I look at the true assembly, your method contains the code "return null", but when I look at the reference assembly, I see no code as you do. / comments
I think this is probably because you are looking at a "reference assembly" instead of the real framework assembly. Reference Assemblies, stored in C:\Program Files\Reference Assemblies, contain the...
Thanks for reporting this. I've logged it as bug RP-725. / comments
Thanks for reporting this. I've logged it as bug RP-725.
Please let me know if I'm wrong, but I think that the code that Reflector generates corresponds to the IL.
In that case, I think the code you give disagrees with Reflector in the case that pageDetails.u.complex.cSections = 0. The Reflector code would bind fssectiondescriptionRef to null, whereas your code would bind fssectiondescriptionRef to the zero element array. / comments
Please let me know if I'm wrong, but I think that the code that Reflector generates corresponds to the IL.
In that case, I think the code you give disagrees with Reflector in the case that pageDeta...
Hi.
I don't think that the generated code is faulty. Both pieces of code return the result of ConnectionString, and both pieces of code only take the lock if the compare result is >= 0. The difference is simply that Reflector isn't generating a body that has an embedded return statement. / comments
Hi.
I don't think that the generated code is faulty. Both pieces of code return the result of ConnectionString, and both pieces of code only take the lock if the compare result is >= 0. The differe...
When you say, "step through", do you mean it displays code that was previously generated by Reflector Pro?
If so, then you need to clear the Reflector Pro cache - you'd normally do this using the "Clear store" button on the "Choose assemblies to debug..." dialog.
You can do the equivalent by:
(i) clearing the directories under C:\Users\clive.tong\AppData\Local\Red Gate\.NET Reflector 6
(ii) clearing the symbol search path by going to Tools/Options... Debugging/Symbols and deleting any symbol file locations that point to these directories. / comments
When you say, "step through", do you mean it displays code that was previously generated by Reflector Pro?
If so, then you need to clear the Reflector Pro cache - you'd normally do this using the "...