Use command-line parameters to install Visual Studio 2017. 10 minutes to read. Contributors.
In this article When you install Visual Studio 2017 from a command prompt, you can use a variety of command-line parameters to control or customize the installation. From the command line, you can perform the following actions:. Start the install with certain options preselected. Automate the installation process.
Create a cache (layout) of the installation files for later use. The command-line options are used in conjunction with the setup bootstrapper, which is the small (approximately 1MB) file that initiates the download process. The bootstrapper is the first executable that is launched when you download from the Visual Studio site. Use the following links to get a direct link to the latest release bootstrapper for the product edition that you're installing:. List of command-line parameters Visual Studio command-line parameters are case-insensitive.
Not Any Good Answers. I continue to look things up and I remembered that this component was installed with Visual Studio,I tried to get the Visual Studio Altogether. Same Problem,it needs 'Microsoft Visual C++ 2012 x64 Minimum Runtime' just like the other installer. Microsoft visual studio 2013 free download - Microsoft Visual Studio 2010 Ultimate, Microsoft Visual Studio 2010 Professional, Visual C++ Redistributable Packages for Visual Studio 2013, and many.
Syntax: vsenterprise.exe command. (Replace vsenterprise.exe as appropriate for the product edition you're installing.). Tip For more examples of how to use the command line to install Visual Studio 2017, see the page.) Command Description (blank) Installs the product. Modify Modifies an installed product. Update Updates an installed product. Repair Repairs an installed product.
Uninstall Uninstalls an installed product. Export New in 15.9: Exports installation selection to an installation configuration file. Note: Can only be used with vsinstaller.exe. Install option Description -installPath The installation directory for the instance to act upon.
For the install command, this is Optional and is where the instance will be installed. For other commands, this is Required and is where the previously installed instance was installed.addProductLang Optional: During an install or modify operation, this determines the UI language packs that are installed to the product. It can appear multiple times on the command line to add multiple language packs. If not present, the installation uses the machine locale. For more information, see the section on this page.removeProductLang Optional: During an install or modify operation, this determines the UI language packs that are to be removed from the product. It can appear multiple times on the command line to add multiple language packs.
For more information, see the section on this page.add Optional: One or more workload or component IDs to add. The required components of the artifact are installed, but not the recommended or optional components. You can control additional components globally using -includeRecommended and/or -includeOptional. To include multiple workloads or components, repeat the -add command (for example, -add Workload1 -add Workload2). For finer-grained control, you can append;includeRecommended or;includeOptional to the ID (for example, -add Workload1;includeRecommended or -add Workload2;includeRecommended;includeOptional).
For more information, see the page. You can repeat this option as necessary.remove Optional: One or more workload or component IDs to remove. For more information, see our page. You can repeat this option as necessary.in Optional: The URI or path to a response file.all Optional: Whether to install all workloads and components for a product.allWorkloads Optional: Installs all workloads and components, no recommended or optional components.includeRecommended Optional: Includes the recommended components for any workloads that are installed, but not the optional components. The workloads are specified either with -allWorkloads or -add.includeOptional Optional: Includes the optional components for any workloads that are installed, but not the recommended components.
The workloads are specified either with -allWorkloads or -add.quiet, -q Optional: Do not display any user interface while performing the installation.passive, -p Optional: Display the user interface, but do not request any interaction from the user.norestart Optional: If present, commands with -passive or -quiet will not automatically restart the machine (if necessary). This is ignored if neither -passive nor -quiet are specified.nickname Optional: This defines the nickname to assign to an installed product. The nickname cannot be longer than 10 characters.productKey Optional: This defines the product key to use for an installed product. It is composed of 25 alphanumeric characters either in the format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx or xxxxxxxxxxxxxxxxxxxxxxxxx.help, -?, -h, -? Display an offline version of this page.config Optional and New in 15.9: During an install or modify operation, this determines the workloads and components to add based on a previously saved installation configuration file.
This operation is additive and it will not remove any workload or component if they are not present in the file. Also, items that do not apply to the product will not be added. During an export operation, this determines the location to save the installation configuration file. Note: When specifying multiple workloads and components, you must repeat the -add or -remove command-line switch for each item. Layout options Description -layout Specifies a directory to create an offline install cache. For more information, see.lang Optional: Used with -layout to prepare an offline install cache with resource packages with the specified language(s). For more information, see the section on this page.add Optional: One or more workload or component IDs to add.
The required components of the artifact are installed, but not the recommended or optional components. You can control additional components globally using -includeRecommended and/or -includeOptional. For finer-grained control, you can append;includeRecommended or;includeOptional to the ID (for example, -add Workload1;includeRecommended or -add Workload2;includeOptional). For more information, see the page. Note: If -add is used, only the specified workloads and components and their dependencies are downloaded. If -add is not specified, all workloads and components are downloaded to the layout.includeRecommended Optional: Includes the recommended components for any workloads that are installed, but not the optional components. The workloads are specified either with -allWorkloads or -add.includeOptional Optional: Includes the recommended and optional components for any workloads being included in the layout.
![]()
The workloads are specified with -add.keepLayoutVersion New in 15.3, optional: Apply changes to the layout without updating the version of the layout.verify New in 15.3, optional: Verify the contents of a layout. Any corrupt or missing files are listed.fix New in 15.3, optional: Verify the contents of a layout. If any files are found to be corrupt or missing, they are redownloaded. Internet access is required to fix a layout.clean New in 15.3, optional: Removes old versions of components from a layout that has been updated to a newer version. Advanced install options Description -channelId Optional: The ID of the channel for the instance to be installed. This is required for the install command, ignored for other commands if -installPath is specified.channelUri Optional: The URI of the channel manifest.
If updates are not desired, -channelUri can point to a non-existent file. (for example, -channelUri C: doesntExist.chman) This can be used for the install command; it is ignored for other commands.installChannelUri Optional: The URI of the channel manifest to use for the installation.
The URI specified by -channelUri (which must be specified when -installChannelUri is specified) is used to detect updates. This can be used for the install command; it is ignored for other commands.installCatalogUri Optional: The URI of the catalog manifest to use for the installation.
If specified, the channel manager attempts to download the catalog manifest from this URI before using the URI in the install channel manifest. This parameter is used to support offline install, where the layout cache will be created with the product catalog already downloaded. This can be used for the install command; it is ignored for other commands.productId Optional The ID of the product for the instance that will be installed. This is prepopulated in normal installation conditions.wait Optional: The process will wait until the install is completed before returning an exit code. This is useful when automating installations where one needs to wait for the install to finish to handle the return code from that install.locale Optional: Change the display language of the user interface for the installer itself.
Setting will be persisted. For more information, see the section on this page.cache New in 15.2, optional: If present, packages will be kept after being installed for subsequent repairs. This overrides the global policy setting to be used for subsequent installs, repairs, or modifications. The default policy is to cache packages. This is ignored for the uninstall command.
Read how to for more information.nocache New in 15.2, optional: If present, packages will be deleted after being installed or repaired. They will be downloaded again only if needed and deleted again after use. This overrides the global policy setting to be used for subsequent installs, repairs, or modifications. The default policy is to cache packages. This is ignored for the uninstall command. Read how to for more information.noUpdateInstaller New in 15.2, optional: If present, prevents the installer from updating itself when quiet is specified.
The installer will fail the command and return a non-zero exit code if noUpdateInstaller is specified with quiet when an installer update is required.noWeb New in 15.3, optional: Setup now downloads any content that it is installing from the Internet. All content that is being installed must be available in an offline layout. If the layout is missing content, setup fails. For more information, see.path = New in 15.7, optional: Used to specify custom install paths for the installation. Supported path names are shared, cache, and install.path cache= New in 15.7, optional: Uses the location you specify to download installation files. This location can only be set the first time that Visual Studio is installed. Example: -path cache='C: VS cache' -path shared= New in 15.7, optional: Contains shared files for side-by-side Visual Studio installations.
Some tools and SDKs install to a location on this drive, while some others might override this setting and install to another drive. Example: -path shared='C: VS shared' Important: This can be set only once and on the first time that Visual Studio is installed.path install= New in 15.7, optional: Equivalent to –-installPath. Specifically, -installPath 'C: VS' and -path install='C: VS' are equivalent. Only one of these can be used at a time. List of workload IDs and component IDs For a list of workload and component IDs sorted by Visual Studio product, see the page.
![]()
Installing the Tableau SDK This topic describes the requirements for using the Tableau SDK and where you can get an installation file. Requirements To work with the Tableau SDK, you need the following:.
For Python, you must have Python 2.x or 3.x installed. On Windows, you must have the Visual C runtime library installed on your computer. You might already have this library installed; for example, it is installed as part of Visual Studio.
If you don't already have the runtime library installed, you can get it from the following page on the Microsoft site: Note: Even if you intend to use Java and Eclipse (that is, you are not going to use C or C, and you are not intending to use Visual Studio), you must still make sure you have the Visual C runtime library installed. The Extract API in the Tableau SDK requires this runtime library. If you are installing on a Mac, you must use the 64-bit installer. If you are installing on Linux: the libpcre16.so.0 package is a required dependency. If you do not have the package installed, which is common on newer versions of Ubuntu, you need to install the latest package and create a symbolic link for the missing file. Follow the instructions for on the page. Downloading the package To get the Tableau SDK, use the appropriate link from the following list.
Windows. (.zip file). (.zip file). (.zip file). (.zip file) Mac OS X. (.tar.gz file). Use this file to install the Python version of the SDK.
(.dmg file). Use this file to install the C, C, and Java versions of the SDK. To use the.dmg file, do the following:.
Open the.dmg file you downloaded. Drag the three files in the Frameworks directory to /Library/Frameworks. You might be asked to enter your password. Drag the License.txt file, the Java folder, and the Samples folder to a location of your choice.
Linux. (.tar.gz file). (.tar.gz file). (.tar.gz file). (.tar.gz file). (.deb file). (.deb file).
(.rpm file). (.rpm file) Setting environment variables Optionally, you can set the following environment variables to specify working directories for the Tableau SDK. If you don't set these variables, the Tableau SDK uses the current working directory as the default location (TMP or TEMP on Windows and the TMPDIR on other systems). Note: The user identity under which code is running must have write permissions to the locations you specify in these environment variables. TABSDKLOGDIR The folder where the Tableau SDK writes log files.
TABSDKTMPDIR The temporary directory where the SDK keeps intermediate (temporary) files, such as when it's creating an extract.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |