[Copilot]

findVersion() threw Invalid version for any toolsVersion due to two independent bugs in msbuild-finder.ts.

Bugs fixed

Pre-v12 versions incorrectly required vswhere.exe

Versions 1.0–4.0 live under C:\Windows\Microsoft.Net\Framework[64]\ — vswhere has no knowledge of them. The old code always called vswhere first; without it, findVersion() returned null.

Fix: Short-circuit for parsedNumber < 12 — call concatPreV12() and check the path directly, no vswhere involved.

V16+ detection used fragile path-substring matching

concatV16AndAbove checked installationPath.includes(MSBUILD_VERSIONS[version]). Works for v16/v17 because VS puts the year (2019, 2022) in the folder. For v18 the mapped value is '18' — any VS whose install folder doesn't contain the literal string '18' (e.g., a future Visual Studio 2026) silently returns '', producing null → Invalid version.

Fix: For major ≥ 16, find the matching installation using installationVersion from the vswhere JSON instead of path substring matching:

const matchingInstallation = installations.find((installation: any) => {
    const installMajor = parseInt(
        (installation.installationVersion || '').split('.')[0] || '0'
    );
    return installMajor === major;
});

This correctly resolves any present or future VS major version regardless of its folder naming convention. concatV16AndAbove and MSBUILD_VERSIONS are left intact as utility helpers.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Doesn't work with MSBuild 18.0</issue_title>
<issue_description>It keeps saying Invalid version no matter what I supply as toolsVersion.</issue_description>

<agent_instructions>It keeps saying Invalid version no matter what I supply as toolsVersion</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Doesn't work with MSBuild 18.0 #13

---

⚡ Quickly spin up Copilot coding agent tasks from anywhere on your macOS or Windows machine with Raycast.