Skip to content

Conversation

@ViktorHofer
Copy link
Member

The netstandard1.3 and net46 configurations of the
System.Security.Cryptography.ProtectedData packages aren't built
anymore. Instead the already built matching binary from the latest
available package version is redistributed when packaging these
libraries.

Dropping the netstandard1.3 asset and the net46 one as the
minimum supported set of platforms are ones that support netstandard2.0.
For .NET Framework, there's still a net461 configuration to avoid
binding redirect issues.

Contributes to #47530

The netstandard1.3 and net46 configurations of the
System.Security.Cryptography.ProtectedData packages aren't built
anymore. Instead the already built matching binary from the latest
available package version is redistributed when packaging these
libraries.

Dropping the netstandard1.3 asset and the net46 one as the
minimum supported set of platforms are ones that support netstandard2.0.
For .NET Framework, there's still a net461 configuration to avoid
binding redirect issues.

Contributes to dotnet#47530
@ghost
Copy link

ghost commented Apr 26, 2021

Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

The netstandard1.3 and net46 configurations of the
System.Security.Cryptography.ProtectedData packages aren't built
anymore. Instead the already built matching binary from the latest
available package version is redistributed when packaging these
libraries.

Dropping the netstandard1.3 asset and the net46 one as the
minimum supported set of platforms are ones that support netstandard2.0.
For .NET Framework, there's still a net461 configuration to avoid
binding redirect issues.

Contributes to #47530

Author: ViktorHofer
Assignees: ViktorHofer
Labels:

area-Infrastructure-libraries

Milestone: 6.0.0

@ViktorHofer ViktorHofer added the breaking-change Issue or PR that represents a breaking API or functional change over a previous release. label Apr 26, 2021
@ghost ghost added the needs-breaking-change-doc-created Breaking changes need an issue opened with https://github.com/dotnet/docs/issues/new?template=dotnet label Apr 26, 2021
@ViktorHofer ViktorHofer merged commit d03dcdd into dotnet:main Apr 26, 2021
@ViktorHofer ViktorHofer deleted the CryptoProtectedHarvesting branch April 26, 2021 18:34
@ghost ghost locked as resolved and limited conversation to collaborators May 26, 2021
@ViktorHofer ViktorHofer removed the needs-breaking-change-doc-created Breaking changes need an issue opened with https://github.com/dotnet/docs/issues/new?template=dotnet label Sep 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Infrastructure-libraries breaking-change Issue or PR that represents a breaking API or functional change over a previous release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants