问题
Say I have several .NET assemblies and want to sign each of them with a strong name. Is one keypair (one .snk file) enough or do I need to generate one pair for each assembly? Will I have to publish the public key of (each) keypair?
回答1:
You need only one .snk file.
You don't need to publish the public key. Any one can get a public key using sn.exe with -p switch.
回答2:
One key file is enough to sign multiple related assemblies. Take a look through your GAC. Assemblies from the same product or platform often all have the same key. For example many of Microsoft's .NET framework assemblies share the same key.
回答3:
We have (3) .snk files.
One that we use to sign our assemblies, one that was shipped for on-site code generation (we don't need to do that anymore), and mono.snk to sign Mono.Cecil and Mono.Security (these are built here for use with Microsoft's .NET).
来源：https://stackoverflow.com/questions/798041/how-many-snk-files-do-i-need