Skip to content
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

Remove pinning to NET7 SDK #17035

Merged
merged 1 commit into from
Aug 28, 2023
Merged

Remove pinning to NET7 SDK #17035

merged 1 commit into from
Aug 28, 2023

Conversation

PureWeen
Copy link
Member

Description of Change

The main branch builds find with the .NET 8 SDK, so there's no reason to require/pin it to NET7.

- The main branch builds find with the NET 8 sdk so there's no reason to require/pin it to NET7
@rmarinho rmarinho enabled auto-merge (squash) August 28, 2023 17:52
Comment on lines -9 to -12
"sdk": {
"version": "7.0.200",
"allowPrerelease": true,
"rollForward": "major"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing these lines is very similar behavior to it being here. rollForward=major allows it to use .NET 8 SDKs.

Either way, seems fine to just delete these as even the .NET team doesn't really suggest using global.json by default -- it's more of something for working around a problem.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, I was thinking with your edits it should be using .NET8.

But mine was still using .NET 7 when I had these there. I had to delete them in order for VS or the CLI to use .NET8.

image

image

@rmarinho rmarinho merged commit 60bdea7 into main Aug 28, 2023
38 checks passed
@rmarinho rmarinho deleted the remove_global_pinning branch August 28, 2023 20:04
@github-actions github-actions bot locked and limited conversation to collaborators Dec 5, 2023
@samhouts samhouts added the fixed-in-8.0.0-rc.1.9171 Look for this fix in 8.0.0-rc.1.9171 label Aug 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
fixed-in-8.0.0-rc.1.9171 Look for this fix in 8.0.0-rc.1.9171
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants