Clarify that using global.json may not be rare #44667
Merged
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.
Summary
Update the word choice for using global.json to select the SDK. The previous word choice made it sound like using a global.json wasn't recommended and reserved for "rare" situations. In practice, many teams want reproducible builds, and as such need to pin developers to a specific version.
To address the concern that global.json can lead to pinning old versions of the SDK, I added a new section calling out that devs can use tools like
dotnet sdk check
and Dependabot to manage SDK updates.Internal previews