Reverting release/10.0 to VS2022 build queues#11411
Merged
dipeshmsft merged 1 commit intorelease/10.0from Feb 2, 2026
Merged
Conversation
dotnet-policy-service
bot
added
the
PR
Member
Author
|
@akoeplinger, can you review this PR, if the workaround is added correctly ? |
SatwikKrSharma
approved these changes
Feb 2, 2026
pranav-gupta-msft
approved these changes
Feb 2, 2026
akoeplinger
approved these changes
Feb 2, 2026
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
5 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.
Description
Reverting the release/10.0 branch to use VS2022 queue as the new MSVC compiler (v145) dropped support for Server 2012-R@
Testing
CI Build
Customer Impact
.NET 10 is unblocked for Server 2012-R2
Risk
Minimal
Microsoft Reviewers: Open in CodeFlow