Unable to delay sign or test sign an assembly

[aKzenT]

It seems it is not possible to use dnlib to either only add the public key token to the assembly (delay signing) or to sign the assembly with a test key (signing with a key that is not the same as the public key used during delay signing). This is unfortunate as in our corporation we want to obfuscate assemblies and then only sign them on the build server while developers use test key signing as recommended by Microsoft best practices.

[aKzenT]

To add to this, it is also not possible to round trip such assemblies. When loading a delay signed assembly and then directly saving it again, the assemblies will have the "StrongName" flag set in the header, while normally delay signed assemblies do not have the flag set. The same applies to test-signed assemblies.

[0xd4d]

I've added a DelaySign option to ModuleWriterOptions that you can use.

Generate the public key:

sn -p mykey.snk mypublickey.snk

Delay sign it:

var file = @"c:\some\path\DelaySigned.exe";
var snPublicKey = new StrongNamePublicKey(@"c:\some\path\mypublickey.snk");
var ctx = ModuleDef.CreateModuleContext();
var mod = ModuleDefMD.Load(file, ctx);
//...
var opts = new ModuleWriterOptions(mod);
opts.DelaySign = true;
opts.StrongNamePublicKey = snPublicKey;
mod.Write(@"c:\some\path\DelaySigned_new.exe", opts);

[aKzenT]

Great! Thank you very much. Is there also a property to check if a loaded
assembly is delay signed (ModuleDef) and in this case would the writer be
initialized correctly to roundtrip?

Thanks again!

Edit: Removed remark about public key as this is already handled. Was confused about the .snk ending.