R
Raut
Guest
I'm trying to create an offline setup package for VS2017. It fails repeatedly. And each time the bootstrapper (vs_bootstrapper_d15) is started it downloads the installer again, taking an extra 5 minutes per attempt.
How can I tell vs_setup_bootstrapper.exe, or the wrapper (vs_professional.exe) to use a local installer (vs_installer.opc) package instead of downloading it every time from https://aka.ms/vs/15/release/installer?
Alternatively, are there any detailed instructions on how to create an offline installer using "Visual Studio Setup Command Line Utility" directly?
It's unclear how the parameters interact (layout, bootstrapperPath, catalog, productId...), and what corresponds to the workload and component IDs used by the bootstrapper's --add parameter.
(By the way, wouldn't it be simpler and more reliable for the "web installer" to come with the 63MB installer actually included, instead of downloading it every time it starts?)
Continue reading...
How can I tell vs_setup_bootstrapper.exe, or the wrapper (vs_professional.exe) to use a local installer (vs_installer.opc) package instead of downloading it every time from https://aka.ms/vs/15/release/installer?
Alternatively, are there any detailed instructions on how to create an offline installer using "Visual Studio Setup Command Line Utility" directly?
It's unclear how the parameters interact (layout, bootstrapperPath, catalog, productId...), and what corresponds to the workload and component IDs used by the bootstrapper's --add parameter.
(By the way, wouldn't it be simpler and more reliable for the "web installer" to come with the 63MB installer actually included, instead of downloading it every time it starts?)
Continue reading...