4 ms·
> I really wish Microsoft would improve the install/packaging story for their C++ build tools on Windows. Not sure if this is what you mean, but vs_installer.e
by mook 4y ago
> I really wish Microsoft would improve the install/packaging story for their C++ build tools on Windows.
Not sure if this is what you mean, but vs_installer.exe supports command line arguments like --add, so you should be able to craft a giant command line for IT to copy. Used it for work for the NodeJS equivalent of your use case.
- jasomill 4y agoYou can avoid the giant command line by providing a configuration file exported from a “known good” install: From the installer GUI on a machine with the correct set of components installed, click the “More ▼” button, then choose “Export Configuration” and follow the resulting prompts. Alternatively, the installer’s “export” command-line operation does the same thing. To use the resulting config file, either supply its path using the “--config” option to the installer’s “install” and “modify” command-line operations, or apply it from the GUI by clicking “More ▼” and choosing “Import Configuration”. This is also handy in non-IT deployments to quickly replicate an existing VS install on a new machine. Incidentally, even if you are going to go with the “giant command line” approach, the export mechanism is an easy way to figure out a valid set of component IDs to supply on said command line, though it doesn’t necessarily generate the smallest set of component IDs able to produce a given configuration, due to the presence of workload IDs and the fact that component dependencies are automatically installed, even if unspecified.