Skip to content

Commit 7c2ba60

Browse files
committed
Add monikers
1 parent 7889f53 commit 7c2ba60

File tree

1 file changed

+42
-3
lines changed

1 file changed

+42
-3
lines changed

docs/install/automated-installation-with-response-file.md

Lines changed: 42 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Configure installation defaults with a response file
33
description: Create a response JSON file to help automate your Visual Studio installation with default settings for workloads, components, and other installation options.
4-
ms.date: 3/11/2024
4+
ms.date: 10/25/2024
55
ms.topic: conceptual
66
helpviewer_keywords:
77
- response file
@@ -107,7 +107,9 @@ When you create or update a layout, a response.template.json file is also create
107107

108108
## Example customized layout response file content
109109

110-
The following `response.json` file example will initialize a Visual Studio 2019 Enterprise client install to select several common workloads and components, to select both the English and French UI languages, and to have the update location configured to look for sources in a network hosted layout. Note that for Visual Studio 2019, the update location (channelUri) can only be configured during initial installation and cannot be changed after the fact *unless* you use the functionality in the latest installer. Refer to the [Configure policies for enterprise deployments of Visual Studio](configure-policies-for-enterprise-deployments.md#configuring-source-location-for-updates) and the [Configure your layout to always include and provide the latest installer](create-a-network-installation-of-visual-studio.md#configure-the-layout-to-always-include-and-provide-the-latest-installer) for information on how to configure this.
110+
The following `response.json` file example will initialize a Visual Studio Enterprise client install to select several common workloads and components, to select both the English and French UI languages, and to have the update location configured to look for sources in a network hosted layout. Note that for Visual Studio 2019, the update location (channelUri) can only be configured during initial installation and cannot be changed after the fact *unless* you use the functionality in the latest installer. Refer to the [Configure policies for enterprise deployments of Visual Studio](configure-policies-for-enterprise-deployments.md#configuring-source-location-for-updates) and the [Configure your layout to always include and provide the latest installer](create-a-network-installation-of-visual-studio.md#configure-the-layout-to-always-include-and-provide-the-latest-installer) for information on how to configure this.
111+
112+
::: moniker range="=vs-2019"
111113

112114
```Example response.json
113115
{
@@ -141,8 +143,44 @@ The following `response.json` file example will initialize a Visual Studio 2019
141143
]
142144
}
143145
```
146+
::: moniker-end
147+
148+
::: moniker range="=vs-2022"
149+
150+
```Example response.json
151+
{
152+
"installChannelUri": ".\\ChannelManifest.json",
153+
"channelUri": "\\\\server\\share\\layoutdirectory\\ChannelManifest.json",
154+
"installCatalogUri": ".\\Catalog.json",
155+
"channelId": "VisualStudio.17.Release",
156+
"productId": "Microsoft.VisualStudio.Product.Enterprise",
144157

145-
In the following example, the `response.json` file initializes a Visual Studio 2022 Enterprise client install that:
158+
"installPath": "C:\\VS2022",
159+
"quiet": false,
160+
"passive": false,
161+
"includeRecommended": true,
162+
"norestart": false,
163+
"useLatestInstaller": true,
164+
"removeOos": true,
165+
166+
"addProductLang": [
167+
"en-US",
168+
"fr-FR"
169+
],
170+
171+
"add": [
172+
"Microsoft.VisualStudio.Workload.ManagedDesktop",
173+
"Microsoft.VisualStudio.Workload.Data",
174+
"Microsoft.VisualStudio.Workload.NativeDesktop",
175+
"Microsoft.VisualStudio.Workload.NetWeb",
176+
"Microsoft.VisualStudio.Workload.Office",
177+
"Microsoft.VisualStudio.Workload.Universal",
178+
"Component.GitHub.VisualStudio"
179+
]
180+
}
181+
```
182+
183+
In the following example, the `response.json` file initializes a Visual Studio Enterprise client install that:
146184
- [Uses a configuration *.vsconfig file that defines what workloads, components, and extensions to install](import-export-installation-configurations.md#use-a-configuration-file-to-initialize-the-contents-of-a-layout)
147185
- Selects both the English and French UI languages
148186
- Configures the [update location to look for sources in an http hosted layout](create-a-network-installation-of-visual-studio.md#making-your-layout-accessible-via-an-intranet-site)
@@ -174,6 +212,7 @@ In the following example, the `response.json` file initializes a Visual Studio 2
174212

175213
}
176214
```
215+
::: moniker-end
177216

178217
> [!WARNING]
179218
> If you're using intranet webhosted layouts, you can’t set “noWeb”: true in the response.json and expect it to work. This will disable the http protocol and prevent the client from accessing the website.

0 commit comments

Comments
 (0)