Backport: Fix VS Release rejecting preview SDKs on Helix test machines #51630
Conversation
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
…rements Co-authored-by: nagilson <23152278+nagilson@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Backport VS release fix to 8.0.3xx
Backport: Fix VS Release rejecting preview SDKs on Helix test machines
Nov 7, 2025
Copilot finished work on behalf of
nagilson
November 7, 2025 23:22
nagilson
approved these changes
Nov 7, 2025
This was referenced Nov 8, 2025
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.
Backports #51558 to
release/8.0.3xx.VS Release rejects preview SDKs by default via a local AppData setting, causing MSBuild SDK resolver failures during Helix test runs.
Changes
eng/enable-preview-sdks.ps1(new): Locates VS installation and setsUsePreviews=Truein the instance-specificsdk.txtfilebuild/RunTestsOnHelix.cmd: Invokes enable-preview-sdks.ps1 before test executioneng/common/tools.ps1: Handles nullvsRequirementsinLocateVisualStudio()when global.json lackstools.vskeyContext
MSBuild respects VS settings when resolving SDKs. Without this fix, internal preview SDKs fail to resolve in test environments using VS Release installations.
Co-authored-by: nagilson 23152278+nagilson@users.noreply.github.com
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.