I found the information about how to do Enhanced Strong Naming from the command line at:
https://msdn.microsoft.com/en-us/library/hh415055(v=vs.110).aspx
That looks like just what I need. I want to sign with Enhanced Strong Naming (ESN), with key migration, because I want to be able to issue new versions of existing assemblies with ESN, and have them be recognised as the same assembly. Command-line is exactly what I need, because I'm working with a build environment that does not and cannot use Visual Studio projects, at all, in any way, and hence MSBuild techniques are no use to me.
However, there's a step in the instructions that looks wrong: Step 4 of "Signing with SHA-2, with Key Migration". It says:
4. Generate the parameters for a AssemblySignatureKeyAttribute attribute, and attach the attribute to the assembly.
sn -ac IdentityPubKey.snk IdentityKey.snk SignaturePubKey.snk
I can't see how this does anything to the assembly. It's just working with the key files, and the assembly doesn't exist at this stage in the process anyway.
Can anyone explain this?
A secondary question: how can I verify that an assembly has an Enhanced Strong Name?
John Dallman