Which, frankly, is huge! The length of the command-line poses an immediate issue as it’s longer than that allowed in the text box for the installation program for an application. Mu_visual_studio_enterprise_2017_x86_圆4_10049783.exe -add includeOptional includeRecommended -add includeOptional includeRecommended -add includeOptional includeRecommended -add includeOptional includeRecommended -add -add -add -add -add includeOptional includeRecommended -add includeOptional includeRecommended -add includeOptional includeRecommended -add includeOptional includeRecommended -add includeOptional includeRecommended -add includeOptional includeRecommended -add -add includeOptional includeRecommended -add -add .WPF -add -add .3.5.DeveloperTools -add -add .CodedUITest -add .Core -add .FeedbackClient -add .MicrosoftTestManager -add .WebLoadTest -add .2.0 -quiet -norestart -wait add includeOptional includeRecommendedĪs you can see, this means that the command-line has the potential to get long very quickly! For the workloads and components I was asked to deploy with Visual Studio Enterprise 2017, our command-line became A list of the Visual Studio 2017 workload and component IDs can be found at (click through to the product you’re installing, for us this was Visual Studio Enterprise 2017, workload and component IDs for which are found at ) For example, to add the Azure development workload, with all optional and recommended components, you’d add the following to the command-line that you issue to the installer: Visual Studio uses this latter approach to selecting the components that will be installed with the product, but the system has been extended to provide more control over the component installation, with an ‘IncludeRecommended’ and ‘IncludeOptional’ flag available for each component, or globally, as required. With Visual Studio 2015 I could not make this approach work at all, and ended up specifying the components to be installed by using the ‘/InstallSelectableItems’ command-line parameter, which worked a treat. With Visual Studio 2013 this worked fine for me. In the past I’ve tried using an AdminDeployment.xml file to control which components of Visual Studio are installed. See for information on the available command-line parameters. The command-line parameters of the Visual Studio 2017 installer are also different to previous versions as well, requiring a different approach. Visual Studio 2017 arrives as a web installer only (although you can create installation media using the –layout option from the command line if you still want to go down that route).
#Visual studio 2017 application wizard iso#
Previous versions of Visual Studio were typically delivered via ISO files that we could import into Configuration Manager for deployment to workstations.
0 kommentar(er)
