Skip to content

Conversation

@ViktorHofer
Copy link
Member

The netstandard1.0 and portable* configurations of the
System.Composition.* 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.0 asset and the portable* 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

@ViktorHofer ViktorHofer requested review from Anipik and ericstj April 21, 2021 09:42
@ViktorHofer ViktorHofer self-assigned this Apr 21, 2021
@ghost
Copy link

ghost commented Apr 21, 2021

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

Issue Details

The netstandard1.0 and portable* configurations of the
System.Composition.* 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.0 asset and the portable* 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-System.Composition

Milestone: -

@ViktorHofer ViktorHofer force-pushed the CompositionHarvesting branch from 2220cf4 to df8073f Compare April 22, 2021 10:44
The netstandard1.0 and portable* configurations of the
System.Composition.* 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.0 asset and the portable* 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
@ViktorHofer ViktorHofer force-pushed the CompositionHarvesting branch from df8073f to 9149592 Compare April 22, 2021 11:41
@ViktorHofer
Copy link
Member Author

Failure is #30056

@ViktorHofer ViktorHofer merged commit bfb0b8a into dotnet:main Apr 22, 2021
@ViktorHofer ViktorHofer deleted the CompositionHarvesting branch April 22, 2021 13:47
@ericstj ericstj added the breaking-change Issue or PR that represents a breaking API or functional change over a previous release. label Apr 22, 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 22, 2021
@karelz karelz added this to the 6.0.0 milestone May 20, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jun 19, 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-System.Composition 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.

4 participants