-
Notifications
You must be signed in to change notification settings - Fork 186
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
Remove legacy dependency System.Security.Cryptography.Algorithms
for netstandard2.1
target
#223
Comments
Hey @OronDF343 , thanks for note, i'll double check. |
You could also just add a target for the latest .NET LTS version in addition to .NET Standard 1.6 and 2.0 for .NET framework and older stuff. |
Hi @EraYaN , probably can, why not. Curious, how it can be helpful though? Aren't .netstandatad2.1 package compatible with LTS versions? |
The problem is that it then includes a whole host of extra dependencies (all the 4.3.0 version) many of which are very much out of support and insecure. You really want to use the newer standard lib. That .NET Standard 1.6.1 thing pulls in tons of stuff. So it's not only a new target, it's also cleaning the deps for that target. |
This package already has a The reference to |
Can double check if
|
@OronDF343 , removed Still thinking about |
The reference to
System.Security.Cryptography.Algorithms
should not be required for thenetstandard2.1
target. In general, anySystem.*
packages with version4.3.x
are meant for .NET Core 1.x based platforms only. I believe that this dependency can be safely removed, and will clean up the list of installed transient dependencies for modern platforms.The text was updated successfully, but these errors were encountered: