All 15 Assemblies & NuGet questions
More in Assemblies & NuGet
What is an assembly in .NET, and what does it contain? What is NuGet, and what problem does it solve for .NET developers? What is the Global Assembly Cache (GAC), and is it still relevant in modern .NET? How does NuGet resolve version conflicts when two packages depend on different versions of the same transitive dependency? How do you create and publish your own NuGet package from a class library project? What is the difference between a NuGet package's dependency group targeting different frameworks, and why do multi-targeted packages need this? What is a NuGet lock file (packages.lock.json), and what problem does it solve for reproducible builds? What are NuGet package sources, and how do you configure a project to pull packages from a private/internal feed alongside NuGet.org? What is Central Package Management (CPM) in NuGet, and how does Directory.Packages.props centralize version control? How does semantic versioning apply to NuGet packages, and what do version range operators like [1.0,2.0) mean?
Advertisement
Back to results for “.NET vs .NET Framework”
.NET › Assemblies & NuGet

What is strong naming of assemblies, and why is it much less commonly required in modern .NET?

Intermediate

Answer

Strong naming signs an assembly with a public/private key pair, giving it a unique identity (name, version, culture, public key token) primarily used historically for GAC installation and preventing assembly substitution/tampering in .NET Framework. Modern .NET's side-by-side, per-application deployment model and absence of a GAC removes most of the original motivations for strong naming, though it's still occasionally required for specific interop scenarios or organizational policy.
<PropertyGroup>
  <SignAssembly>true</SignAssembly>
  <AssemblyOriginatorKeyFile>MyKey.snk</AssemblyOriginatorKeyFile>
</PropertyGroup>
Real-world example A library targeting both legacy Framework consumers (who still expect strong-named assemblies for GAC compatibility) and modern .NET consumers maintains strong naming primarily for backward compatibility rather than any modern security need.

Common follow-ups: Does strong naming provide real security guarantees on its own?;When would a modern .NET project still need strong naming?

Assemblies & NuGet;.NET vs .NET Framework
All 15 Assemblies & NuGet questions