Skip to content
Open core software, built in Singapore Established 2018  /  Five utilities
Jering
Talk to us

Strong Naming

DevOps.AzurePipelines Jering documentation Open source Pipeline templates
Documentation menu

Strong naming gives an assembly a cryptographic identity. It solves some problems and creates others, so make the choice deliberately.

What it does

A strong name includes a public key and a signature over the assembly. On .NET Framework it participates in binding and the global assembly cache. Modern .NET still records the identity but relies less on it for loading.

Tradeoffs

A strong name can make assembly binding stricter. It does not prove that the code is trustworthy on its own; the private key must be protected. If the project does not need the identity, adding it later can be disruptive.

Make the decision early

If public consumers depend on the assembly identity, decide before the first stable release. Changing a strong name afterwards is a breaking change for everyone who references the assembly.

Reference shelf