R – How many .snk files do I need

netstrongname

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?

Best Answer

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.

Related Solutions

C# – How to enumerate an enum

foreach (Suit suit in (Suit[]) Enum.GetValues(typeof(Suit)))
{
}

Note: The cast to (Suit[]) is not strictly necessary, but it does make the code 0.5 ns faster.

R – Do I need to publish the public key from .snk file

No, you don't need to publish your public key outside of the assembly since it is hashed and stored as a token alongside the reference inside the client's application:

AssemblyName, Version=1.0.0.0, Culture=neutral, PublicKeyToken=bcd6707151635d07"

This gives a method to ensure that all future versions of the assembly are compiled against the same key pair and therefore from the same publisher.

More details about how having this information stops another source from pretending to be you can be found in my other answer.

Best Answer

Related Solutions

C# – How to enumerate an enum

R – Do I need to publish the public key from .snk file

Related Topic