-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Upgrading the netcoreapp2.x and netcoreapp3.0 build configurations to netcoreapp3.1 #53358
Conversation
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue Detailsprojects to netcoreapp3.1 and cleaning up conditions so that future Adding NETStandardError markers to prevent available netstandard2.0 For more details please see the reasoning in the linked issue. Contributes to #53282
|
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
9687281
to
fa10975
Compare
There was a problem hiding this 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
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