-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
Add netcoreapp3.0 target for nbgv #277
Milestone
Comments
I can add this as a PR |
It would be nice to be able to do this:
But it does not currently work:
|
Closed
Merged
AArnott
pushed a commit
that referenced
this issue
Aug 8, 2024
Bumps [powershell](https://github.com/PowerShell/PowerShell) from 7.4.3 to 7.4.4. - [Release notes](https://github.com/PowerShell/PowerShell/releases) - [Commits](PowerShell/PowerShell@v7.4.3...v7.4.4) --- updated-dependencies: - dependency-name: powershell dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
.NET Core global tools will auto roll-forward to the next minor. So for people that only have
netcoreapp2.2
, the currentnetcoreapp2.1
target will work just fine. Major versions do not roll forward, so if a user only hasnetcoreapp3.0
, then the tool will fail.The solution is to either have users with both a .NET Core 2.x SDK and a 3.x SDK or to have tools multi-target. For ease of users, I'm recommending all .NET Core global tools add a
netcoreapp3.0
target./cc @KathleenDollard
The text was updated successfully, but these errors were encountered: