Skip to content

Conversation

@jonthysell
Copy link
Contributor

@jonthysell jonthysell commented Jul 16, 2024

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

Microsoft Reviewers: Open in CodeFlow

@jonthysell jonthysell marked this pull request as ready for review July 16, 2024 22:33
@jonthysell jonthysell requested review from a team as code owners July 16, 2024 22:33
@jonthysell
Copy link
Contributor Author

Note: This won't pass until the VM image refresh completes, but that will be a good test that the PR fails when it detects the current VM image doesn't have the right VS version.

@jonthysell jonthysell requested a review from a team as a code owner July 18, 2024 16:34
@jonthysell
Copy link
Contributor Author

Tried to bump us to 17.10.4, but it looks like it breaks our native unit tests: https://developercommunity.visualstudio.com/t/VS2022-17101-throws-an-error-in-Azure-/10678969

So end users should be unblocked by 17.10.4, but we can't update the repo until maybe 17.10.5.

@jonthysell jonthysell changed the title Bump minimum VS version to 17.10.4 Bump minimum VS version to 17.10.5 Jul 31, 2024
@jonthysell
Copy link
Contributor Author

Tried to bump to 10.17.5, but now DeployAppRecipe is broken again.

@jonthysell jonthysell changed the title Bump minimum VS version to 17.10.5 Bump minimum VS version to 17.11.0 Aug 14, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the New Architecture Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric label Aug 14, 2024
@jonthysell
Copy link
Contributor Author

Updating this PR to require the just released 17.11.0. Waiting for the test image to refresh so I can validate everything's clear, then I'll update the main image.

@jonthysell jonthysell added Developer First Experience Issues that are going to be hit by a new developer as they first try out RNW Area: Developer Experience Scenario: Visual Studio and removed New Architecture Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric labels Aug 15, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the New Architecture Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric label Aug 15, 2024
@jonthysell jonthysell enabled auto-merge (squash) August 15, 2024 21:33
@jonthysell jonthysell merged commit 4bb42ec into microsoft:main Aug 15, 2024
@jonthysell jonthysell deleted the vs17104 branch August 16, 2024 17:10
jonthysell added a commit to jonthysell/react-native-windows that referenced this pull request 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 pull request 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 pull request 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 pull request 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 pull request 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 pull request 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 pull request 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 pull request 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 pull request 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

Area: Developer Experience Developer First Experience Issues that are going to be hit by a new developer as they first try out RNW New Architecture Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric Scenario: Visual Studio

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

Unable to build e2e-test-app-fabric with VS 2022 Preview 17.11 Unable to deploy RNW app after upgrade to VS 17.10.2

2 participants