Add .NET 5.0 target #2246
Merged
Add .NET 5.0 target #2246
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It looks like the 5.0 SDK included in Appveyor's "Visual Studio 2019 Preview" image is still the RC1 version and not the final version, so I'll wait until they update it to the final version before merging. |
ob-stripe
force-pushed
the
ob-target-net5
branch
3 times, most recently
from
2b8fe05
to
400d92b
Compare
ob-stripe
force-pushed
the
ob-target-net5
branch
from
400d92b
to
af960e7
Compare
|
Appveyor added .NET 5.0 to the Visual Studio 2019 image (cf. https://www.appveyor.com/updates/2020/11/14/). I've also updated the ptal @richardm-stripe |
ob-stripe
commented
Nov 16, 2020
richardm-stripe
approved these changes
Dec 9, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
r? @richardm-stripe
.NET 5.0 was released today. Microsoft recommends that reusable libraries add it as a build target but still keep targeting .NET Standard 2.0 as well for backwards compatibility.