fix arcade and .NET 3 SDK #6765
Merged
Conversation
This file contains hidden or 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
added 2 commits
May 14, 2019 12:24
…513.3 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19263.3
…514.13 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19264.13
brettfo
force-pushed
the
arcade-net3
branch
3 times, most recently
from
1a90f09 to
59e328f
Compare
This changes our build to mark all of our .NET Core applications as rolling forward on major / minor versions of the .NET framework. Presently our tools ship inside both .NET Core 2 and 3 SDKs. This setting allows our tools to run unmodified in both settings.
Member
Author
|
@KevinRansom and @cartermp: Note that with the latest arcade changes we require a preview of .NET Core 3 SDK. I've added a link in |
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.
Attempt to make #6727 work.