Obfuscate Excel Add-in

Add-in Express™ Support Service
That's what is more important than anything else

Obfuscate Excel Add-in
 
Andrew Saunders




Posts: 17
Joined: 2006-03-21
When I try and rename the Assembly I get the following message.
"MyAddin.dll does not represent a strongly named assembly".

Any ideas on why I am getting this?

Posted 05 Jul, 2006 23:39:33 Top
Sergey Grischenko


Add-in Express team


Posts: 7235
Joined: 2004-07-05
Hi Andrew.

The fact is that the Aspose.Obfuscator doesn't recognize delay signed assemblies. Please set the AssemblyDelaySign attribute to false in the AssemblyInfo.cs file, rebuild the add-in and obfuscate it in the Aspose.Obfuscator. Then use the command line mentioned above to re-sign the add-in.
Posted 06 Jul, 2006 06:57:51 Top
Andrew Saunders




Posts: 17
Joined: 2006-03-21
I did all that and unfortunately I still get the same message when I try to re-sign the assembly.
Posted 06 Jul, 2006 07:54:10 Top
Sergey Grischenko


Add-in Express team


Posts: 7235
Joined: 2004-07-05
Do you have the MyAddin.snk file included in the add-in project?

[assembly: AssemblyKeyFile("..\\..\\MyAddin.snk")]
Posted 06 Jul, 2006 07:58:43 Top
Andrew Saunders




Posts: 17
Joined: 2006-03-21
yes.
Posted 06 Jul, 2006 08:37:09 Top
Sergey Grischenko


Add-in Express team


Posts: 7235
Joined: 2004-07-05
Andrew, please use the ILDasm.exe tool to see if the add-in is strongly named. You should see the '.publickey = (...)' field in the MANIFEST dialog of the ILDasm tool.
Posted 06 Jul, 2006 09:51:44 Top
Andrew Saunders




Posts: 17
Joined: 2006-03-21
I have sorted it out. I needed to supply the full path to both the dll and to the key file in inverted commas to the sn.exe tool. Then it re-signed successfully and installs without errors.

Thanks for all your help.
Posted 06 Jul, 2006 22:48:26 Top