Upgrade to 2.2 #106
Open
Upgrade to 2.2 #106
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
Contributor
|
Heave you check all dependent project, I remember the CSS on the fly building has a missing package, it was on December 2018 |
MattLavalleeMA
suggested changes
Feb 18, 2019
MattLavalleeMA
left a comment
MattLavalleeMA
left a comment
There was a problem hiding this comment.
The metapackage Version attribute should no longer be specified (as of 2.1).
Contributor
|
Yes, for an Upgrade to the actual Version we need a (empty) Implementation of all functions as asynchronous one. |
Co-Authored-By: smulholland2 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
This PR does some of the basic steps in upgrading to .NET Core 2.2, based on https://docs.microsoft.com/en-us/aspnet/core/migration/21-to-22.