Skip to content

Conversation

@logiclrd
Copy link
Contributor

Adds a mapping for Visual Studio 2026 to the cmakeGenerator property used to drive Windows builds, enabling Flutter to be used for development on a system with Visual Studio 2026 installed and not Visual Studio 2022 or Visual Studio 2019.

Closes: #176399
Related-To: #93426

Pre-launch Checklist

  • I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
  • I read the [Tree Hygiene] wiki page, which explains my responsibilities.
  • I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
  • I signed the [CLA].
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is [test-exempt].
  • I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
  • All existing and new tests are passing.

@github-actions github-actions bot added tool Affects the "flutter" command-line tool. See also t: labels. a: desktop Running on desktop labels Oct 23, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds support for Visual Studio 2026 by mapping its version number to the appropriate CMake generator string. Additionally, it includes a test case to verify the correct CMake generator is selected when Visual Studio 2026 is detected. The code changes look correct, and the addition of the test case is good. However, the version number 2026 is hardcoded, and there is no way to configure it. I have added a review comment to address this.

@logiclrd
Copy link
Contributor Author

Regarding the precise values used in the _vs2026Response data for the test:

MINGW64 $ ./vswhere -prerelease | grep -E 'displayName|installationVersion|productDisplayVersion'
installationVersion: 18.0.11116.177
displayName: Visual Studio Community 2026
catalog_productDisplayVersion: Insiders [11116.177]

MINGW64 $

@logiclrd logiclrd changed the title Add support for Visual Studio 2022 Add support for Visual Studio 2026 Oct 23, 2025
@loic-sharma loic-sharma self-requested a review October 25, 2025 06:33
@bkonyi bkonyi added the team-windows Owned by the Windows platform team label Oct 29, 2025
Copy link
Member

@loic-sharma loic-sharma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing this!

@loic-sharma loic-sharma requested a review from bkonyi October 30, 2025 22:11
@bkonyi bkonyi added the autosubmit Merge PR when tree becomes green via auto submit App label Oct 31, 2025
@auto-submit auto-submit bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Oct 31, 2025
@auto-submit
Copy link
Contributor

auto-submit bot commented Oct 31, 2025

autosubmit label was removed for flutter/flutter/177458, because The base commit of the PR is older than 7 days and can not be merged. Please merge the latest changes from the main into this branch and resubmit the PR.

…r property in visual_studio.dart.

Added a test for the Visual Studio 2026 mapping to visual_studio_test.dart.
@logiclrd
Copy link
Contributor Author

Huh. Weird. Git says that upstream master doesn't share any history in common with my fork master, and as such, it isn't possible to merge the latest upstream master into this branch. I hope it's okay to just re-apply this commit onto upstream master using cherry-pick and force-push the branch.

@loic-sharma
Copy link
Member

I checked the Google testing failures, they looked like flakes unrelated to your change. Rerunning...

@loic-sharma loic-sharma added the autosubmit Merge PR when tree becomes green via auto submit App label Nov 1, 2025
@auto-submit auto-submit bot added this pull request to the merge queue Nov 1, 2025
Merged via the queue into flutter:master with commit 7b1bafe Nov 1, 2025
146 of 147 checks passed
@flutter-dashboard flutter-dashboard bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Nov 1, 2025
@logiclrd
Copy link
Contributor Author

logiclrd commented Nov 1, 2025

🎉

engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 3, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 3, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 3, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 3, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 3, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 4, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 4, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 4, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 4, 2025
@Pktangle

This comment was marked as off-topic.

@selvam920

This comment was marked as off-topic.

@linkec

This comment was marked as off-topic.

@JacoNeto

This comment was marked as off-topic.

@Pktangle

This comment was marked as off-topic.

@JacoNeto

This comment was marked as off-topic.

@Pktangle

This comment was marked as off-topic.

@bkonyi bkonyi added cp: beta cherry pick this pull request to beta release candidate branch cp: stable cherry pick this pull request to stable release candidate branch labels Nov 13, 2025
flutteractionsbot pushed a commit to flutteractionsbot/flutter that referenced this pull request Nov 13, 2025
Adds a mapping for Visual Studio 2026 to the `cmakeGenerator` property
used to drive Windows builds, enabling Flutter to be used for
development on a system with Visual Studio 2026 installed and not Visual
Studio 2022 or Visual Studio 2019.

Closes: flutter#176399
Related-To: flutter#93426

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [x] I listed at least one issue that this PR fixes in the description
above.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.
@flutteractionsbot
Copy link

Failed to create CP due to merge conflicts.
You will need to create the PR manually. See the cherrypick wiki for more info.

@bkonyi bkonyi removed the cp: beta cherry pick this pull request to beta release candidate branch label Nov 13, 2025
@bkonyi
Copy link
Contributor

bkonyi commented Nov 13, 2025

This change was submitted after the 3.38 stable release was branched. I've created a cherrypick request to have this included in the 3.38.2 release (assuming 3.38.1 is released to resolve #178400).

bufffun pushed a commit to bufffun/flutter that referenced this pull request Nov 26, 2025
Adds a mapping for Visual Studio 2026 to the `cmakeGenerator` property
used to drive Windows builds, enabling Flutter to be used for
development on a system with Visual Studio 2026 installed and not Visual
Studio 2022 or Visual Studio 2019.

Closes: flutter#176399
Related-To: flutter#93426

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [x] I listed at least one issue that this PR fixes in the description
above.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.
reidbaker pushed a commit to AbdeMohlbi/flutter that referenced this pull request Dec 10, 2025
Adds a mapping for Visual Studio 2026 to the `cmakeGenerator` property
used to drive Windows builds, enabling Flutter to be used for
development on a system with Visual Studio 2026 installed and not Visual
Studio 2022 or Visual Studio 2019.

Closes: flutter#176399
Related-To: flutter#93426

## Pre-launch Checklist

- [x] I read the [Contributor Guide] and followed the process outlined
there for submitting PRs.
- [x] I read the [Tree Hygiene] wiki page, which explains my
responsibilities.
- [x] I read and followed the [Flutter Style Guide], including [Features
we expect every widget to implement].
- [x] I signed the [CLA].
- [x] I listed at least one issue that this PR fixes in the description
above.
- [x] I updated/added relevant documentation (doc comments with `///`).
- [x] I added new tests to check the change I am making, or this PR is
[test-exempt].
- [x] I followed the [breaking change policy] and added [Data Driven
Fixes] where supported.
- [x] All existing and new tests are passing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a: desktop Running on desktop cp: stable cherry pick this pull request to stable release candidate branch team-windows Owned by the Windows platform team tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Support for VisualStudio 2026

8 participants