Support MS Build 17 (Visual Studio 2022) #326
Open
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.
Description
Adds MS Build 17 support (included with Visual Studio 2022).
Related Issue
#312
Motivation and Context
We have MS Build 16 and 17 installed on multiple TeamCity build agents, but the behavior of selecting the used version is not identical on all agents. Some of them select MS Build 17 as desired, while others select version 16, which lacks support for newer C# language versions, for example.
How Has This Been Tested?
Tested on TeamCity build agents of the company I'm consulting for.
Builds now succeed on agents that were failing before.
Types of changes
Note: Selecting MS Build 17 could perhaps arguably be considered a breaking change. In some edge cases our project files required some adjustments to make them build. However, the fact that the user installed the new version probably means they want to use it.
Checklist: