|
Hello, I am currently evaluating the visual studio reflector. I initially got a message saying refector's version of the assembly is not loaded and I may not be able to debug it. So, I added reference to the regenerated assembly from reflector but then the project would not compile and I got the message as : Could not load file or assembly 'xyz, Version=4.0.0.0, Culture=neutral, PublicKeyToken=vfsfsfsxxxxx' or one of its dependencies. Strong name signature could not be verified. The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045) Please advise if this obstacle can be overcome and if so, the right sequence of steps that needs to be followed to load reflector's assembly at the right time . I look forward to your assistance. |
|
We'll need more information about what you are doing - the type of project for example. We do Regeneration when you want to debug an assembly that doesn't contain a debugger signature - typically something produced in release mode where the user has changed the default setting of "debug info:" to none, or perhaps as the result of a post processing obfuscation step. We need to add the debugger signature, but as you see, this invalidates the strong name signature. We get around this by putting the modified assembly in a directory which we add to the DEVPATH - this is treated as part of the GAC in that there is no check on the signature when the assembly is loaded, allowing us to add the debugger signature (so VS can link the generated pdb and the assembly). |
