Skip to content

Conversation

@ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented May 27, 2021

Upgrading the netcoreapp2.x and netcoreapp3.0 build configurations to netcoreapp3.1
and cleaning up conditions so that future tfm upgrades require less project file changes.

Adding NETStandardError markers to prevent available netstandard2.0 assets being picked
instead, same as already done for System.Speech and others.

For more details please see the reasoning in the linked issue.

Contributes to #53282

@ViktorHofer ViktorHofer added area-Infrastructure-libraries breaking-change Issue or PR that represents a breaking API or functional change over a previous release. labels May 27, 2021
@ViktorHofer ViktorHofer added this to the 6.0.0 milestone May 27, 2021
@ViktorHofer ViktorHofer requested review from Anipik and ericstj May 27, 2021 15:37
@ViktorHofer ViktorHofer self-assigned this May 27, 2021
@ghost
Copy link

ghost commented May 27, 2021

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

Issue Details

projects to netcoreapp3.1 and cleaning up conditions so that future
tfm upgrades require less project file changes.

Adding NETStandardError markers to prevent available netstandard2.0
assets being picked instead, same as already done for System.Speech
and others.

For more details please see the reasoning in the linked issue.

Contributes to #53282

Author: ViktorHofer
Assignees: ViktorHofer
Labels:

area-Infrastructure-libraries, breaking-change

Milestone: 6.0.0

@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 May 27, 2021
Upgrading the netcoreapp2.x and netcoreapp3.0 build configurations in
projects to netcoreapp3.1 and cleaning up conditions so that future
tfm upgrades require less project file changes.

Adding NETStandardError markers to prevent available netstandard2.0
assets being picked instead, same as already done for System.Speech
and others.

For more details please see the reasoning in the linked issue.

Contributes to dotnet#53282
Copy link
Contributor

@Anipik Anipik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple of comments, other than that looks good

@ghost ghost locked as resolved and limited conversation to collaborators Jun 27, 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.

2 participants