MSBuild vs17.6->vs16.7 merges (aka 17.7 -> 17.8 from VS perspective)#895
Merged
mmitche merged 1 commit intodotnet:mainfrom Jun 19, 2023
Merged
MSBuild vs17.6->vs16.7 merges (aka 17.7 -> 17.8 from VS perspective)#895mmitche merged 1 commit intodotnet:mainfrom
mmitche merged 1 commit intodotnet:mainfrom
Conversation
rainersigwald
approved these changes
Jun 19, 2023
mmitche
approved these changes
Jun 19, 2023
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
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.
Context
17.7 is being locked down; development on 17.8 will continue in main
This is cc of the #875 PR
Changes made
MSBuild vs17.6 (so far latest release branch) will now flow to vs17.7 (newest release branch from now on) and vs17.7 changes will flow to main
cc @rainersigwald as FYI