Use single .NET SDK version in pipelines #13719
Merged
Conversation
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
9b22c11
to
4114ab5
Compare
jmacato
approved these changes
Nov 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does the pull request do?
This PR ensures that the same .NET 7.0 SDK version is used in all build pipelines and on developer machines, by using
global.jsonas the single source of truth..NET 6 is installed as runtime only (to run tests), making it clearer that the .NET 6 SDK isn't used (and saving a few seconds of installation time).
What is the current behavior?
Multiple different SDK versions (7.0.101, 7.0.402) are used.
6 different locations in 3 files must be edited to change the SDK everywhere.