I am able to install non-obfuscated delay-signed assemblies to the GAC. When I attempt to install obfuscated delay-signed assemblies to the GAC then I get the error message:
"Failure adding assembly to the cache: Strong name signature could not be verified. Was the assembly built delay-signed?"
1) I have just started working with shared assemblies for the first time. I would like confirmation that it is to be expected that delay-signed assemblies with signing verification disabled (i.e.: sn.exe -Vr "myAssemblyName.dll") can be installed in the GAC. In other words, the fact that I am able to do this on my computer is normal and not somehow an anomaly.
2) When writing/developing delay-signed assemblies, is the 'best practice' to install/test/debug the assembly in the GAC or to test/debug the assembly in the project's local output directory?
3) As mentioned, I can successfully install a delay-signed assembly in the GAC when it is non-obfuscated. But when I obfuscate the delay-signed assembly and attempt to install it in the GAC then I get the error message reported above. Is there anything special I need to do in this case to install the obfuscated, delay-signed assembly in the GAC? Some additional information:
a) I am working with Visual Studio 2013, ultimate
b) the delay-signed C# assembly is obfuscated in the project's post-build event
c) the obfuscator I am using is ConfuserEX (https://yck1509.github.io/ConfuserEx/)
d) in the project's post-build event, immediately after obfuscating the project's assembly, I attempt to install the assembly in the GAC using the 32 bit version of gacutil.exe.
e) I am developing under Win7 64 bits
ThanX for all suggestions and comments