Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/standard/library-guidance/strong-naming.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,9 @@ You should strong name your open-source .NET libraries if their targets include
> [!NOTE]
> This guidance is specific to publicly distributed .NET libraries, such as .NET libraries published on NuGet.org. Strong naming is not required by most .NET applications and should not be done by default.

✔️ CONSIDER strong naming your library's assemblies.
✔️ CONSIDER strong naming your library's assemblies if you target .NET Framework or .NET Standard.

> Strong naming has no impact on modern .NET Runtimes, so if you only target .NET then you can skip it.

✔️ CONSIDER adding the strong naming key pair (public + private) to your source control system.

Expand Down
Loading