-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add Visual Studio 2026 support in CI pipelines and CLI #15426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
protikbiswas100
wants to merge
17
commits into
microsoft:main
Choose a base branch
from
protikbiswas100:cherrypick-vs2026
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add Visual Studio 2026 support in CI pipelines and CLI #15426
protikbiswas100
wants to merge
17
commits into
microsoft:main
from
protikbiswas100:cherrypick-vs2026
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: protikbiswas100 <[email protected]>
Co-authored-by: protikbiswas100 <[email protected]>
Co-authored-by: protikbiswas100 <[email protected]>
Co-authored-by: protikbiswas100 <[email protected]>
Co-authored-by: protikbiswas100 <[email protected]>
Co-authored-by: protikbiswas100 <[email protected]>
Co-authored-by: protikbiswas100 <[email protected]>
Co-authored-by: protikbiswas100 <[email protected]>
…adapter.yml Co-authored-by: protikbiswas100 <[email protected]>
…annel change file
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.
Description
Type of Change
Why
Users with only VS2026 installed cannot run
npx @react-native-community/cli run-windowsbecause the CLI and CI pipelines are hardcoded for VS2022 (version 17.x). VS2026 uses version 18.x with platform toolset v145. The CLI was searching for VS with version range[17.11.0,18.0)which excludes VS2026.Resolves #15387
What
vsInstalls.tsto extend the version range from[17.11.0,18.0)to[17.11.0,19.0)when minVersion is 17.x, allowing both VS2022 (17.x) and VS2026 (18.x) to be detectedhealthCheckList.ts: Display text now shows "Visual Studio 2022/2026" instead of just "Visual Studio 2022".ado/image/rnw-img-vs2026-node22.jsonwith VS bootstrapper URLhttps://aka.ms/vs/18/release/vs_Enterprise.exe(configuration template for infrastructure team to build and deploy)rnw-img-vs2026-node22:windows-vs-pr.yml,windows-vs-pr-secure.yml,continuous.yml,compliance.yml,publish.ymlintegrate-rn.yaml: Changed vmImage fromwindows-2022towindows-2025(latest available Azure DevOps hosted image -windows-2026does not exist)msbuild-sln.yml:msbuildVersion: 17.0→18.0platformToolset: v143→v145discover-google-test-adapter.yml: VS path updated to useMicrosoft Visual Studio\18\Enterprise(VS2026 installs to version-numbered folder18, not2026)vnext/Scripts/rnw-dependencies.ps1:17.11.0to18.0.0Microsoft.VisualStudio.2022.*toMicrosoft.VisualStudio.2026.*AutomationChannel.sln- VisualStudioVersion from 17.x to 18.xAutomationChannel.vcxproj- MinimumVisualStudioVersion from 17.0 to 18.0UsesPackageReference.csproj- MinimumVisualStudioVersion from 17.0 to 18.0UsesPackagesConfig.vcxproj- MinimumVisualStudioVersion from 17.0 to 18.0react-native-windows,@react-native-windows/cli,@react-native-windows/automation-channel, and@react-native-windows/telemetrypackages)Note: The CI pipeline changes require the infrastructure team to build and deploy the
rnw-img-vs2026-node22image to the Azure DevOps agent pools before CI will work with VS2026. The CLI changes for local development with VS2026 are immediately functional.This change follows the same pattern as the VS2019 to VS2022 upgrade in commit 5885ee4.
Screenshots
Testing
The CLI fix allows users with VS2026 to successfully run
npx @react-native-community/cli run-windowsfor local development. CI pipeline changes will be validated once the infrastructure team builds and deploys thernw-img-vs2026-node22agent image to the Azure DevOps pools.Changelog
Should this change be included in the release notes: yes
Added Visual Studio 2026 support. The CLI now detects both VS2022 (17.x) and VS2026 (18.x). CI pipelines and project files updated to require VS2026 with platform toolset v145 (requires infrastructure team to deploy the new agent image).
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
Microsoft Reviewers: Open in CodeFlow