Merge pull request #10590 from MicrosoftDocs/release-17.4

Release 17.4 merge to main

Author: ghogen

docs/code-quality/roslyn-analyzers-overview.md

@@ -1,5 +1,5 @@
 ---
-title: Code analysis using Roslyn analyzers
+title: Code analysis using Roslyn analyzers 
 ms.date: 01/15/2022
 description: Become familiar with source code analysis in Visual Studio. Learn about code fixes and the different types of analyzers and severity levels.
 ms.custom: SEO-VS-2020, devdivchpfy22

docs/install/applying-administrator-updates.md

@@ -1,7 +1,7 @@
 ---
 title: Automate installation with a response file
-description: Learn how to create a JSON response file that helps you automate your Visual Studio installation
-ms.date: 12/7/2021
+description: Learn how to create a response JSON file that helps you automate your Visual Studio installation
+ms.date: 11/3/2022
 ms.topic: conceptual
 helpviewer_keywords:
 - response file
@@ -96,7 +96,7 @@ When you create or update a layout, a response.template.json file is also create
 
 ::: moniker range="=vs-2019"
 
-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 point back to the 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 [Set defaults for enterprise deployments of Visual Studio](set-defaults-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.
+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 the 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 [Set defaults for enterprise deployments of Visual Studio](set-defaults-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.
 
 ```Example response.json
 {
@@ -111,7 +111,7 @@ The following `response.json` file example will initialize a Visual Studio Enter
   "passive": false,
   "includeRecommended": true,
   "norestart": false,
-
+  
   "addProductLang": [
     "en-US",
     "fr-FR"
@@ -133,7 +133,7 @@ The following `response.json` file example will initialize a Visual Studio Enter
 
 ::: moniker range="=vs-2022"
 
-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 point back to the layout. 
+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, to always remove components that have transitioned to out of support when the client is being updated, and to have the update location configured to look for sources in the layout. See the list of out-of-support components [here](out-of-support-components.md).
 
 ```Example response.json
 {
@@ -148,6 +148,7 @@ The following `response.json` file example will initialize a Visual Studio Enter
   "passive": false,
   "includeRecommended": true,
   "norestart": false,
+  "removeOos": true,
 
   "addProductLang": [
     "en-US",

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

@@ -1,7 +1,7 @@
 ---
 title: Command-line parameter examples for installation
 description: Customize these examples to create your own command-line installation of Visual Studio.
-ms.date: 3/3/2022
+ms.date: 11/3/2022
 ms.topic: conceptual
 ms.assetid: 837F31AA-F121-46e9-9996-F8BCE768E579
 author: anandmeg
@@ -18,11 +18,11 @@ ms.technology: vs-installation
 
 To illustrate how to [use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md), here are several examples that you can customize to match your needs.
 
-In each example, `vs_enterprise.exe`, `vs_professional.exe` and `vs_community.exe` represent the respective edition of the Visual Studio bootstrapper, which is the small (approximately 1MB) file that initiates the download process. If you are using a different edition, substitute the appropriate bootstrapper name.
+In each example, `vs_enterprise.exe`, `vs_professional.exe` and `vs_community.exe` represent the respective edition of the Visual Studio bootstrapper, which is the small (~1MB) file that initiates the download process. If you're using a different edition, substitute the appropriate bootstrapper name.
 
-All commands require administrative elevation, and a User Account Control prompt will be displayed if the process is not started from an elevated prompt.
+All commands require administrative elevation, and a User Account Control prompt will be displayed if the process isn't started from an elevated prompt.
 
-You can use the `^` character at the end of a command line to concatenate multiple lines into a single command. Alternatively, you can simply place these lines together onto a single row. In PowerShell, the equivalent is the backtick (`` ` ``) character.
+You can use the `^` character at the end of a command line to concatenate multiple lines into a single command. Alternatively, you can place these lines together onto a single row. In PowerShell, the equivalent is the backtick (`` ` ``) character.
 
 For lists of the workloads and components that you can install by using the command line, see the [Visual Studio workload and component IDs](workload-and-component-ids.md) page.
 
@@ -47,7 +47,7 @@ For lists of the workloads and components that you can install by using the comm
 
 ## Update in two steps
 
-* Update a Visual Studio instance via the command line, with no interactive prompts but progress displayed. If the bootstrapper is on the client machine, then you can run this from the client. Otherwise, you will need to run this from the layout. The first command updates the installer, and the second command updates the Visual Studio product.
+* Update a Visual Studio instance via the command line, with no interactive prompts but progress displayed. If the bootstrapper is on the client machine, then you can run this command from the client. Otherwise, you'll need to run this command from the layout. The first command updates the installer, and the second command updates the Visual Studio product.
 
    ```shell
    vs_enterprise.exe --update --quiet --wait
@@ -59,7 +59,7 @@ For lists of the workloads and components that you can install by using the comm
 
 ## Using --wait
 
-* Use `--wait` in batch files or scripts to wait for the Visual Studio installer to complete before the next command is executed. For batch files, an `%ERRORLEVEL%` environment variable will contain the return value of the command, as documented in the [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md) page. Some command utilities require additional parameters to wait for completion and to get the installer's return value. The following is an example of the additional parameters used with the PowerShell script command 'Start-Process':
+* Use `--wait` in batch files or scripts to wait for the Visual Studio installer to complete before the next command is executed. For batch files, an `%ERRORLEVEL%` environment variable will contain the return value of the command, as documented in the [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md) page. Some command utilities require additional parameters to wait for completion and to get the installer's return value. The following command is an example of the additional parameters used with the PowerShell script command 'Start-Process':
 
    ```shell
    start /wait vs_professional.exe --installPath "C:\VS" --passive --wait > nul
@@ -87,15 +87,15 @@ For lists of the workloads and components that you can install by using the comm
 
 ## Using --layout to create a network layout or a local cache
 
-* Download the Visual Studio core editor (the most minimal Visual Studio configuration). Only include the English language pack:
+* Create a layout that includes only the Visual Studio core editor (the most minimal Visual Studio configuration) and the English language pack:
 
   ```shell
    vs_professional.exe --layout C:\VS ^
    --lang en-US ^
    --add Microsoft.VisualStudio.Workload.CoreEditor
   ```
 
-* Download the .NET desktop and .NET web workloads along with all recommended components. Only include the English language pack:
+* Create a layout that includes the .NET desktop and .NET web workloads, along with all recommended components, English only.
 
   ```shell
    vs_professional.exe --layout C:\VS ^
@@ -123,7 +123,7 @@ For lists of the workloads and components that you can install by using the comm
   ```
 
 ## Using --channelURI
-Using the Visual Studio 2022 or later installer, it is possible to [configure where Visual Studio looks for updates](/visualstudio/install/update-visual-studio?view=vs-2022&preserve-view=true#configure-source-location-of-updates-1). This is otherwise known as the update channel or the source location of updates. The following table gives example values for channelURI and what they mean.
+Using the Visual Studio 2022 or later installer, it's possible to [configure where Visual Studio looks for updates](/visualstudio/install/update-visual-studio?view=vs-2022&preserve-view=true#configure-source-location-of-updates-1). The `--channelURI` is otherwise known as the update channel or the source location of updates. The following table gives example values for channelURI and what they mean.
 
 | **Channel Name** | **--channelURI** |
 |------------------|------------------|
@@ -134,37 +134,44 @@ Using the Visual Studio 2022 or later installer, it is possible to [configure wh
 | Visual Studio 2017 Release channel | `https://aka.ms/vs/15/release/channel` |
 | Custom layout - Private Channel | `\\layoutserver\share\path\channelmanifest.json` |
 
-If you choose to use a custom layout as the update channel, then be aware of the following:
+If you choose to use a custom layout as the update channel, then be aware of the following guidelines:
   * the --channelURI must point to the 'channelmanifest.json' file in the custom layout. 
   * Administrators can configure [how the custom layout "Private Channel" is displayed in the Update Settings UI by configuring the client's registry settings](/visualstudio/install/set-defaults-for-enterprise-deployments#configuring-source-location-for-updates). 
 
 ## Using --remove
 
-::: moniker range="vs-2019"
-
 * Remove the Profiling Tools component from the default installed Visual Studio instance:
 
   ```shell
    vs_enterprise.exe modify ^
-   --installPath "C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise" ^
+   --installPath "C:\Program Files\Microsoft Visual Studio\2022\Enterprise" ^
    --remove Microsoft.VisualStudio.Component.DiagnosticTools ^
    --passive
   ```
 
-::: moniker-end
+## Using --removeOos
+>[!NOTE]
+>This command requires using the VS 2022 version 17.4 or later installer. Follow the guidance here for [how to acquire the latest installer on your client machine](/install/update-visual-studio.md#install-the-latest-and-greatest-installer).
 
-::: moniker range=">=vs-2022"
-
-* Remove the Profiling Tools component from the default installed Visual Studio instance:
+* Modify an installation and remove all [components that have transitioned to an out-of-support state](out-of-support-components.md) from the default installed Visual Studio instance:
 
   ```shell
    vs_enterprise.exe modify ^
    --installPath "C:\Program Files\Microsoft Visual Studio\2022\Enterprise" ^
-   --remove Microsoft.VisualStudio.Component.DiagnosticTools ^
+   --removeOos true ^
    --passive
   ```
 
-::: moniker-end
+* Adjust the update settings to persistently remove all components that have transitioned to an out-of-support state every time the product updates:
+
+  ```shell
+  vs_enterprise.exe modifySettings ^
+  --channelURI https://aka.ms/vs/17/release.LTSC.17.0/channel ^
+  --productID Microsoft.VisualStudio.Product.Enterprise ^
+  --newChannelURI \\layoutserver\share\path\channelmanifest.json ^
+  --removeOos true ^
+  --quiet  
+  ```
 
 ## Using --path
 
@@ -218,5 +225,5 @@ If you choose to use a custom layout as the update channel, then be aware of the
 
 * [Visual Studio Administrator Guide](visual-studio-administrator-guide.md)
 * [Use command-line parameters to install Visual Studio](use-command-line-parameters-to-install-visual-studio.md)
-* [Create an offline installation of Visual Studio](create-an-offline-installation-of-visual-studio.md)
+* [Create a network installation of Visual Studio](create-a-network-installation-of-visual-studio.md)
 * [Visual Studio workload and component IDs](workload-and-component-ids.md)