-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Update strong naming guidance for .NET libraries to only apply to applicable platforms #49026
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
gewarren
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a suggestion for consideration. Thanks for adding this!
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.
Since Strong Naming has no impact on modern .NET Runtimes, limit the scope of guidance to .NET Framework and .NET Standard
Internal previews