Update strong naming guidance for .NET libraries to only apply to applicable platforms #49026
+5
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…licable platforms Since Strong Naming has no impact on modern .NET Runtimes, limit the scope of guidance to .NET Framework and .NET Standard
There was a problem hiding this comment.
Pull Request Overview
Updates strong naming guidance for .NET libraries to clarify that it only applies to .NET Framework and .NET Standard, not modern .NET runtimes. This change helps developers understand when strong naming is actually necessary.
- Modified the primary recommendation to specify targeting .NET Framework or .NET Standard
- Added explanatory note that strong naming has no impact on modern .NET runtimes
DamianEdwards
approved these changes
Oct 8, 2025
gewarren
approved these changes
Oct 8, 2025
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
If multitargeting, strong naming should be done for all TFMs so that InternalsVisibleTo attributes can remain consistent.
jkotas
reviewed
Oct 8, 2025
|
|
||
| ## Create strong named .NET libraries | ||
|
|
||
| You should strong name your open-source .NET libraries if their targets include .NET Framework or .NET Standard. Strong naming is not required for libraries that target .NET Core/5+ only. |
There was a problem hiding this comment.
Suggested change
| Strong naming is not required for libraries that target .NET Core/5+ only. You should strong name your open-source .NET libraries if their targets include .NET Framework or .NET Standard. |
We should lead with ,NET Core.
jkotas
reviewed
Oct 8, 2025
|
|
||
| Strong naming has no benefits on .NET Core/5+. C# compiler produces CS8002 warning for strong-named assemblies referencing non-strong named assemblies. It is fine to suppress this warning for libraries that target .NET Core/5+ only. | ||
|
|
||
| ## Create strong named .NET libraries |
There was a problem hiding this comment.
Suggested change
| ## When to strong name .NET libraries |
I think this should be a question, not a directive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Strong Naming has no impact on modern .NET Runtimes, limit the scope of guidance to .NET Framework and .NET Standard
Internal previews