microsoft / microsoft/microsoft-ui-xaml
Remove the VS 2022 setup flow and standardize WinUI setup on VS 2026
- Dominant language
- C++
- Stars
- 8.4k
- Forks
- 942
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 105
Description
Update the WinUI development setup to use a single Visual Studio 2026-based flow.
Scope:
- Identify all documentation and scripts that install, configure or reference Visual Studio 2022 Build Tools.
- Review whether the VS 2022-specific MSBuild path in `OneTimeSetup.cmd` can be removed.
- Update or remove related setup scripts and documentation as appropriate.
- Provide one clear setup flow using Visual Studio 2026.
- Review `.vsconfig` and `.vsconfig_buildtools` for the components required by VS 2026.
- Review how `init.cmd` discovers, installs and updates build tooling.
- Validate initialization and a complete build on a clean VS 2026 machine.
- Ensure internal build and pipeline scenarios continue to work.
Contributor guide
Research direction
Read OneTimeSetup.cmd, init.cmd, .vsconfig, and .vsconfig_buildtools first, then inventory the documentation and scripts that reference Visual Studio 2022 Build Tools. Done means one clear Visual Studio 2026 setup flow, initialization and a complete build succeeding on a clean machine, and internal build and pipeline scenarios remaining functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system, desktop, documentation, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100