Huh?
You can't delaysign the assembly, obfuscate it, and then re-sign it?
I've never tried this, but I'd have thought you should be able to do
this, that's what delay-sign is for...
Even the help "obfuscating, strong-named assemblies" says:
"Strong named assemblies are digitally signed. This allows the runtime
to determine if an assembly has been altered after signing. The
signature is an SHA1 hash signed with the private key of an RSA
public/private key pair. Both the signature and the public key are
embedded in the assembly's metadata.
Since Dotfuscator modifies the assembly, it is essential that signing
occur after running the assembly through Dotfuscator. You should delay
sign the assembly during development and before Dotfuscation, then
complete the signing process afterward. See the .NET Framework
documentation for more details about delay signing assemblies. Remember
to turn off strong name validation while testing your delay signed
assemblies!"
jliu
Fabio Z wrote:
"SharpCoderMP" <cs*******@interia.pl.NFSPMha scritto nel messaggio
you have to resign your dll's after obfuscation. if you are using
dotfuscator community edition shipped with VS, then you're out of luck.
That's what I thinked :(
I wonder why the dotfuscator don't warning about this, and I don't know why
the obfuscated assembly seems to be resigned right :(
Ok... maybe I'll do the trick using ngen in place of the offuscation.
Thanks