Jakub Bereżański

It seems that the VS Installer, before it quits with exit code 0, launches a separate process (which eventually lanuches additional processes) in order to 1) updates the installer, 2)...

Hi Dan, Your solution seems sound and the command line appears to be correct. The VS Installer generates a lot of log files which usually quickly point to the cause...

The line you point to is simply calling the actual the VS installation program. The official [VS 2017 system requirements](https://docs.microsoft.com/en-us/visualstudio/releases/2017/vs2017-system-requirements-vs) page does not list Server 2022 as supported, so we...

> This idea won't work for community edition since the legacy bootstrappers are not uploaded. Actually, all that's needed are the proper channel and component manifest json files. The bootstrappers...

I intend to: - bump the major version numbers of the current packages (which always install the latest version) to 100+ range, e.g. 116.8.2 instead of 16.8.2 - (eventually, when...

https://github.com/aminya/setup-cpp/blob/7fdcafd80517c9878f7cd4b8dc0ef296a6836070/src/msvc/msvc.ts#L51 ``` "add Microsoft.VisualStudio.Workload.NativeDesktop --includeRecommended --passive", ``` I'm pretty certain there should be a `--` before `add`. The way visualstudio2019buildtools package parameters parsing works is that all switches are recognized...

Second issue: "Microsoft.VisualStudio.Workload.NativeDesktop" is the id of the workload for the full IDE, not for Build Tools. For Build Tools you probably want the "Microsoft.VisualStudio.Workload.VCTools" workload (see https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-build-tools?view=vs-2019&preserve-view=true#desktop-development-with-c).

Lastly, I suggest installing the workload using its own addon package: `visualstudio2019-workload-vctools` instead of passing --add in the main package parameters. This both reduces the complexity of package parameters and...

After fixing the workload installation, I can see that this toolset version gets installed: `14.29.30133` (C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133) but your script uses `toolset = "16.11.2.0"`. I'm not a...

I suggest you try installing the packages by hand (just typing the choco commands and the vcvarsall.bat invocation into cmd) on a clean system and inspect the result. Also, I...