Same problem: xxx.dll does not represent a strongly named assembly
Here is what we did:
1. checked "Delay Sign only" while kept "Sign the assembly" check
2. built, got UnsignedAddin.dll
3. ran Outlook, add-in cannot load
4. manualy sign from commoand line OK: ran sn -R unsignedAddin.dll
keyfile.pfx
5. ran Outlook, addin loaded OK.
6. built again
7. obfuscate the UnsignedAddin.dll =>ObfuscatedUnsignedAddin.dll
8. ran sn -R ObfuscatedUnsignedAddin.dll keyfile.pfx
Got error message: obfuscatedUnsignedAddin.dll does not represent a strongly
named assembly
<kenslovak@mvps.org> wrote in message
news:u%23uSfKFuJHA.4444@TK2MSFTNGP04.phx.gbl...
> Any time you obfuscate you must delay sign your assembly and actually sign
> it with that SNK or PFX after the obfuscation. Otherwise the
> signature/strong naming is also obfuscated along with your code.
> >
>
> "Jason" <a@a.com> wrote in message
> news:OmOO8w7tJHA.5452@TK2MSFTNGP02.phx.gbl...
> > Can anyone recommend a obfuscator?
>
>> We tried Xenocode postbuild but got an error: "This assembly is not
> > strong name signed." Looks like the message came out of the
> > RunCaspolCommand method in the CaspolSecurityPolicyCreator.cs of the
> > SetSecurity project.
>
>> Can Dotfuscator handle addin and the security challenge?
>
>>
>