build,win: fix vs2022 compilation

[StefanStojanovic]

When we added VS2026 support, by accident we broke VS2022 compilation if you have both VS2026 and VS2022 installed (eg, you had to provide the vs2022 parameter). This PR fixes that bug.

[MikeMcC399]

I checked this out and confirm it was broken before and is now fixed. 👍🏻

I hadn't previously noticed because I hadn't used .\vcbuild with a vs* parameter, even though I had done quite a few related tests!

In a side-by-side installation:

VS Build Tools 2022
- "Desktop development with C++" workload
- MSBuild support for LLVM (clang-cl)
- C++ Clang Compiler for Windows (19.1.5)

VS Build Tools 2026
- "Desktop development with C++" workload
- MSBuild support for LLVM (clang-cl)
- C++ Clang Compiler for Windows (20.1.8)

Command	Result before	Result after
.\vcbuild	starts using 2026	starts using 2026
.\vcbuild vs2022	fails to start	starts using 2022
.\vcbuild vs2026	starts using 2026	starts using 2026

---

Edit: fixed
@StefanStojanovic There's a misplaced comma in your original post, as it sounds like VS2026 support was added by accident.

[StefanStojanovic]

@StefanStojanovic There's a misplaced comma in your original post, as it sounds like VS2026 support was added by accident.

You are right, I haven't noticed that. It is changed now.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/71065/