Support Visual Studio 2026
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 616
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
In contrast, our entire build process depends on Visual Studio 2022. We have several options:
- #10884 Disadvantage: pinned image may vanish one nice day
- #10881 Disadvantage: longer build time (but that's overshadowed by longer Linux build time)
- #10878 Disadvantage: we have to either support multiple VS versions or switch to v2026
Tasks
- Add VS 2026 compatibility to the build scripts in this repo (TBD: should they continue to work with other versions?)
- Update the GitHub runner image to a newer version as it was downgraded by #10884 as a workaround for GitHub changing the VS version in the
windows-2025image.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the build scripts responsible for Visual Studio 2022 compatibility and the GitHub Actions configuration for the windows-2025 runner image. Check the related issues #10884, #10881, and #10878 for context. Done means the build scripts support Visual Studio 2026 and the runner image is updated without losing the required build support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github-actions
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100