Make it possible to obfuscate a signed assembly.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Obfuscate a signed assembly.

What version of the product are you using? On what operating system?
Latest release.

Please provide any additional information below.
It would be nice to be able to force obfuscation (or warn instead of fail)
of signed assemblies.
The assembly would then need to be resigned with sn.exe but it would make
it possible to avoid making delay-signed assemblies.

As I said before, great product!

Original issue reported on code.google.com by mikael.hansen.idevio@gmail.com on 12 Dec 2008 at 11:26

[GoogleCodeExporter]

Original comment by mikael.hansen.idevio@gmail.com on 26 May 2009 at 9:52

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Attached is a patch to actually support signing. It adds a new:

<Var name="KeyFile" value="Path\to\file.snk" />

variable. It needs the latest Cecil (0.6) to do it's work, and it needs
Mono.Security.dll/Mono.Security.Win32.dll from any recent mono version. Both 
are MIT
licensed and could be included by default.

Original comment by carlokok@gmail.com on 24 Jun 2009 at 11:04

Attachments:

• support_for_key_signing.patch

[GoogleCodeExporter]

Thats great. It works. My first try with subversion, mono, and obfuscar and I 
managed 
to bring all the bits together - this patch works a treat.

Thanks

Original comment by adam%wyl...@gtempaccount.com on 12 Aug 2009 at 11:06

[GoogleCodeExporter]

I applied the patch and added the Mono.Security.dll and Mono.Security.Win32.dll 
files.
It is included in version 1.5, but I did not check if it works.

Original comment by webbi...@gmail.com on 6 Nov 2009 at 2:57

• Changed state: Fixed