[danoli3]

of vsconfig could install VS 2022 and 2026 through winget, but winget has no VS 2019 package, so VS 2019 only got a download link.

Changes

• install_vs_components.sh installs any of 2019 / 2022 / 2026 from Microsoft's aka.ms Community bootstrapper with that year's .vsconfig, and only runs it when it has a valid Microsoft signature. ARM64 tools are still added for 2022/2026 on ARM hosts.
• Installer exit 3010 (restart needed) arrives in Git Bash as 194, so a successful install that wanted a reboot was reported as FAIL. Both now count as success.
• The of menu vsconfig picker marks each VS as installed or — install.
• of help explains that of vsconfig can install a missing Visual Studio.

Tested

• VS 2019 installed on a real machine with the same bootstrapper and 2019.vsconfig; the core and a projectGeneratorCmd -pvs2019 project then built and ran in Debug and Release with VS 2019's MSBuild.
• Signature check against the real bootstrapper (accepted) and an unsigned file (rejected, never launched).
• Install flow with downloads and installs stubbed: correct link and config for each version, restart-needed, cancelled and download-failure handling, and no install without a terminal or with --check.
• Menu labels and choices with all three versions installed and with none installed, using stubbed checks.
• bash -n and git diff --check passed.

Not tested: this script's own download-and-install of VS 2022 or 2026 on a machine without them, or the menu picker on a machine without them.