Add global.json file to lock SDK version #2104
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
Add a global.json file to the project to make it clearer that we should be using _at least_ version 8.x of the .NET SDK. This can help when building locally without a valid .NET Runtime version installed, to make it clear what the issue is. We set the roll-forward policy to `latestMajor` meaning we will look for any SDK major version from the set version forward. In this case, since we set 8.0, this will match 8.x, 9.x, 10.x etc. When we move to a newer runtime target (probably `net10.0`) we'll want to bump this minimum SDK version to 10.0. Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com>
xfabo1
approved these changes
Nov 6, 2025
dscho
approved these changes
Nov 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Add a global.json file to the project to make it clearer that we should be using at least version 8.x of the .NET SDK. This can help when building locally without a valid .NET Runtime version installed, to make it clear what the issue is.
We set the roll-forward policy to
latestMajormeaning we will look for any SDK major version from the set version forward. In this case, since we set 8.0, this will match 8.x, 9.x, 10.x etc.When we move to a newer runtime target (probably
net10.0) we'll want to bump this minimum SDK version to 10.0.