-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Obsoleting StrongNameKeyPair type in .NetCore #6343
Comments
The Obsoletion will be added only into .Net 6. So if this type and API is not referenced from .Net 6 context then there will be no issue |
|
@buyaa-n We looked at this in triage. If we do reference it in .NET 5/6, we should be able to ifdef it out. Thanks for the heads up. |
Thanks, @rainersigwald the PR for obsoleting |
As part of dotnet/runtime#47228 we are obsoleting APIs not supported in .Net Core. The APIs we are obsoleting in reflection are listed in dotnet/runtime#50529. Where we found that
System.Reflection.StrongNameKeyPair
is not supported in .NetCore and existing APIs only throwing PNSE or no-op. We are planning to update the no-op constructor overloads to throw PNSE and[Obsolete]
the entire type. Which also causing to ObsoleteAssemblyName.KeyPair
property. This type and API doesn't have real usage in runtime repo but from https://source.dot.net/ we see it is referenced a lot from MSBuild repo.Please let us know if you have any issue with Obsoleting this type and API
Originally posted by @buyaa-n in dotnet/runtime#50941 (comment)
The text was updated successfully, but these errors were encountered: