View Single Post
  #2  
Old April 8th 09, 02:54 PM posted to microsoft.public.outlook.program_addins
Ken Slovak - [MVP - Outlook]
external usenet poster
 
Posts: 5,848
Default obfuscator problem

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.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Jason" wrote in message
...
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?



Ads