Backport #51558: Fix VS rejecting preview SDKs on Helix test machines #51628
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
Co-authored-by: nagilson <[email protected]>
Copilot
AI
changed the title
[WIP] Backport release fix to version 8.0.1xx
Backport #51558: Fix VS rejecting preview SDKs on Helix test machines
Nov 7, 2025
Copilot finished work on behalf of
nagilson
November 7, 2025 23:17
nagilson
approved these changes
Nov 7, 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.
VS Release instances reject preview SDKs by default, causing MSBuild SDK resolver failures during Helix testing. This backports the fix from #51558 to release/8.0.1xx.
Changes
eng/enable-preview-sdks.ps1(new): Locates VS installations and setsUsePreviews=Truein the instance-specificsdk.txtconfiguration file. Preserves existing settings.build/RunTestsOnHelix.cmd: Invokes the preview SDK enablement script before test execution on Helix machines.eng/common/tools.ps1: Adds null safety toLocateVisualStudio()whenglobal.jsonlacks atools.vssection, preventing failures in repositories without VS requirements.The script targets the VS-versioned LocalAppData directory:
Resolves #51525 for 8.0.1xx release branch.
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.