-
Notifications
You must be signed in to change notification settings - Fork 32
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
Update to lts 31 #17
Closed
Closed
Update to lts 31 #17
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
c43b0dd
Add icon and use PackageIcon as PackageIconUrl is deprectated for rec…
tebeco 0530ec0
use PackageLicenseExpression instead of PackageLicenseUrl (deprecated)
tebeco e60abd9
Update SDK to 3.1.101
tebeco 7ab5ade
this commit is questionable, for now cross target to support both LTS…
tebeco 3a712c8
update appveyor image to vs2019
tebeco adeef67
Remove linter warning from Build.ps1
tebeco b6c57f4
Add the same Setup.ps1 as in Serilog.AspNetCore + update AppVeyor so …
tebeco 4871e1a
remove Private/Include asset, not sure why this was set like this as …
tebeco 0f9418a
target only netstandard2.0
tebeco File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
$ErrorActionPreference = "Stop" | ||
|
||
$RequiredDotnetVersion = $(Get-Content ./global.json | convertfrom-json).sdk.version | ||
|
||
mkdir "./build" | ||
|
||
Invoke-WebRequest "https://dot.net/v1/dotnet-install.ps1" -OutFile "./build/installcli.ps1" | ||
& ./build/installcli.ps1 -InstallDir "$pwd/.dotnetcli" -NoPath -Version $RequiredDotnetVersion | ||
if ($LASTEXITCODE) { exit 1 } | ||
|
||
$env:Path = "$pwd/.dotnetcli;$env:Path" |
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
{ | ||
"sdk": { | ||
"version": "2.2.105" | ||
"version": "3.1.101" | ||
} | ||
} | ||
} |
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
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
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
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.
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.
All these packages are targeted to
netstandard2.0
. No need to multitargeting<TargetFrameworks>netstandard2.0;netcoreapp3.1</TargetFrameworks>.
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.
Ok, that's what was all about my remarks in the comment ;)
That the solution i would prefer too
but that also means that people using
AspNetCore 2.x
won't resolved this assembly anymore and need to pin it to the current version.Can you validate that you are ok with it ?
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.
I don't understand.
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.
This is the Metapackage used for AspNetCore 2.x :
https://www.nuget.org/packages/Microsoft.AspNetCore.App
Open the dependency list, it's built by dependending on
Microsoft.Extension.xxxxx
2.xSo if this nuget stays
netstandard2.0
(As it should, and as you suggest too), and now depends onMicrosoft.Extension.xxxxx
3.x, then not sure what's going to happen.Again the solution for user still using
AspNetCore 2.x
would just be to pin this dependency, that's allThere 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.
That is, in essence, we are talking about two incompatible versions of the package for the same
netstandard2.0
platform? And they are incompatible because of their dependencies, which changed the major version. Right?Then this is really some problem. But you should keep in mind that nothing prevents using the new version of this package with 3.1 dependencies in applications that do not use AspNetCore at all. New 3.1 libs are just upgraded libs but still target to
netstandard2.0
I would say that AspNetCore 2.x users were initially limited by the ability to evolve into new versions of libraries due to restrictions introduced by the authors of this metapackage.
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.
This is basically a Major version change yes, so in order to be ... up to date, people needs to update :D
I always find it funny to say but that basically it :
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.
That is, in any case, we should not retarget the package to netcoreapp3.1. Right?
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.
If the decision is
Remember that .Net 5 is goign to be a big game changer for that ;)
As we speak Mono is being merge in
dotnet/runtime
;)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.
again i insist on the fact that consumer that keeps using
aspnetcore 2.x
have already pinned their own system, so to my eyes, they would also just pin their dependenciesSo yes i'm in favor of target
netstandard2.0
, and move toPackageReference Microsoft.Extensions.xxxx 3.x
But that's not my decision to take
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.
Let's listen to @nblumhardt opinion.