-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Unable to build e2e-test-app-fabric
with VS 2022 Preview 17.11
#13374
Labels
bug
External Developer Tooling
Issue caused by the tool chain, not by RNW itself
New Architecture
Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric
Scenario: Visual Studio
Milestone
Comments
microsoft-github-policy-service
bot
added
the
Needs: Triage 🔍
New issue that needs to be reviewed by the issue management team (label applied by bot)
label
Jun 20, 2024
jonthysell
added
Scenario: Visual Studio
New Architecture
Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric
labels
Jun 20, 2024
chrisglein
added
the
External Developer Tooling
Issue caused by the tool chain, not by RNW itself
label
Jun 24, 2024
chrisglein
removed
the
Needs: Triage 🔍
New issue that needs to be reviewed by the issue management team (label applied by bot)
label
Jun 24, 2024
I have confirmed that 17.11.0 fixes this issue (and other outstanding VS issues) for us. I'm updating our CI images to 17.11.0 now and PR #13455 will bump our dependency script to make sure you have 17.11.0 installed, but everyone should be safe to upgrade to 17.11.0 now. Sorry that this took so long to figure out. |
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Aug 16, 2024
This PR backports microsoft#13455 to 0.75. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Aug 16, 2024
This PR backports microsoft#13455 to 0.74. This PR bumps the minimum version of VS that RNW expects to 17.11.0. - Bug fix (non-breaking change which fixes an issue) To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. N/A `run-windows` now works with 17.11.0. Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Aug 16, 2024
This PR backports microsoft#13455 to 0.74. This PR bumps the minimum version of VS that RNW expects to 17.11.0. - Bug fix (non-breaking change which fixes an issue) To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. N/A `run-windows` now works with 17.11.0. Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Aug 16, 2024
This PR backports microsoft#13455 to 0.73. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
jonthysell
added a commit
to jonthysell/react-native-windows
that referenced
this issue
Aug 16, 2024
This PR backports microsoft#13455 to 0.72. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves microsoft#13339 Resolves microsoft#13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
jonthysell
added a commit
that referenced
this issue
Aug 16, 2024
This PR backports #13455 to 0.75. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves #13339 Resolves #13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
jonthysell
added a commit
that referenced
this issue
Aug 16, 2024
This PR backports #13455 to 0.73. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves #13339 Resolves #13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
jonthysell
added a commit
that referenced
this issue
Aug 16, 2024
This PR backports #13455 to 0.74. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves #13339 Resolves #13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
jonthysell
added a commit
that referenced
this issue
Aug 20, 2024
This PR backports #13455 to 0.72. ## Description This PR bumps the minimum version of VS that RNW expects to 17.11.0. ### Type of Change - Bug fix (non-breaking change which fixes an issue) ### Why To make sure users don't use the regressed builds of VS 2022. Resolves #13339 Resolves #13374 ### What Bumped VS version checks for `run-windows` and `rnw-dependencies.ps1`. Updated ADO image to reflect updated images are no longer locked to VS v17.9.4. ## Screenshots N/A ## Testing `run-windows` now works with 17.11.0. ## Changelog Should this change be included in the release notes: _yes_ Require Visual Studio 2022 >= v17.11.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
External Developer Tooling
Issue caused by the tool chain, not by RNW itself
New Architecture
Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric
Scenario: Visual Studio
Problem Description
In verifying that the current VS preview build, 17.11, fixes issue #13339, I hit this error when trying to build
e2e-test-app-fabric
:Steps To Reproduce
run-windows
uses 17.11 (see AddedMinimumVisualStudioVersion
env variable to forcerun-windows
to use a particular version of VS installed #13373)packages/e2e-test-app-fabric
, runyarn windows --release --logging
Expected Results
App builds and launches.
CLI version
14.0.0-alpha.2
Environment
Community Modules
No response
Target Platform Version
None
Target Device(s)
Desktop
Visual Studio Version
Visual Studio 2022
Build Configuration
Release
Snack, code example, screenshot, or link to a repository
msbuild.binlog.zip
The text was updated successfully, but these errors were encountered: