Comments
Sort by recent activity
I hope that in a future version we'll be able to investigate the expensive storing the meaning of every word in the decompiled source, but we don't have time in this version I'm afraid.
We should be able to hide the context menu item in this situation though. / comments
I hope that in a future version we'll be able to investigate the expensive storing the meaning of every word in the decompiled source, but we don't have time in this version I'm afraid.
We should b...
That's a good suggestion, I've put it in, and it'll be available in a couple of builds time.
I'm glad you've said you use the "Show me this dialog when I start debugging" checkbox. I was thinking of removing it. Does anyone else use it frequently?
Thanks, / comments
That's a good suggestion, I've put it in, and it'll be available in a couple of builds time.
I'm glad you've said you use the "Show me this dialog when I start debugging" checkbox. I was thinking o...
As I said in my other conversation with you at http://www.red-gate.com/messageboard/vi ... php?t=9877 we need to regenerate your main assembly to add a debugger signature. This version is distinguished from the real version because it has no public key (as you noticed).
I can see how the satellite assembly wouldn't get loaded, because it no longer has the same (lack of) public key as the main assembly. You were right to try referencing and decompiling the satellite assembly, that's what I would have tried. The reason it didn't work I believe is because the satellite assembly does have a debugger signature, so reflector didn't regenerate it.
A fix might be to strip the public key from the satellite assembly, then put it in the build output of your project. This looks a hopeful way of doing this: http://www.codeproject.com/KB/security/ ... ove20.aspx
Let me know how that goes if you have time to do that.
I'll look at whether it's possible to automatically detect this situation and fix it.
Thanks, / comments
As I said in my other conversation with you at http://www.red-gate.com/messageboard/vi ... php?t=9877 we need to regenerate your main assembly to add a debugger signature. This version is distingui...
That's a shame, it might mean that it's not possible to have an automatic fix for this. I'll give it a try though. / comments
That's a shame, it might mean that it's not possible to have an automatic fix for this. I'll give it a try though.
I'm not too worried about adding erroneous hint paths when your assembly is in the GAC, as they are ignored and overridden by the GAC anyway. Addin the version number is far more important.
Cheers, / comments
I'm not too worried about adding erroneous hint paths when your assembly is in the GAC, as they are ignored and overridden by the GAC anyway. Addin the version number is far more important.
Cheers,
Hi Daniel,
Thanks a lot for that report, that's an important problem you've found. In case you're interested, it's because we have to create a new version of the reference with a debugger signature added. We then temporarily change your project to point to the regenerated version eg:
<Reference Include="foo, Version=xxx, Culture=neutral, PublicKeyToken=null, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>C:\Users\alex.davies\AppData\Local\Red Gate\.NET Reflector 6\Cache\Regenerated\ACCC3328A4261F2CAFECDCE6E0585F70</HintPath>
</Reference>
during debugging so that debugging works.
We then do our best to put it back how it was before. Up til now, we thought that we would always leave it at least equivalent to before (not necessarily the same). But I understand how pointing to the same dll isn't enough.
I'll look into it, and hopefully it'll be possible to fix without sacrificing the ease of use we have at the moment.
Cheers,[/b] / comments
Hi Daniel,
Thanks a lot for that report, that's an important problem you've found. In case you're interested, it's because we have to create a new version of the reference with a debugger signature...
Could you send me the assembly in question?
Thanks, / comments
Could you send me the assembly in question?
Thanks,
Yes, Reflector doesn't use the actual folder location, it finds it out, so a reinstall from the Integration Options should do the trick. / comments
Yes, Reflector doesn't use the actual folder location, it finds it out, so a reinstall from the Integration Options should do the trick.
Oh, I thought it worked on VS2010. I have it installed here, and test it occasionally. Might have broken in this build though.
The "Browse" button to add non-referenced assemblies to decompile should still be there. / comments
Oh, I thought it worked on VS2010. I have it installed here, and test it occasionally. Might have broken in this build though.
The "Browse" button to add non-referenced assemblies to decompile shou...
Have you tried the .NET Reflector 6 EAP? http://www.red-gate.com/messageboard/vi ... .php?f=109 / comments
Have you tried the .NET Reflector 6 EAP?http://www.red-gate.com/messageboard/vi ... .php?f=109