Merge branch 'main' into repo_sync_working_branch

Author: ghogen

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

@@ -24,7 +24,7 @@ ms.workload:
 
 Analyzers are divided into the following groups:
 
-- [Code style](/dotnet/fundamentals/code-analysis/code-style-rule-options?preserve-view=true&view=vs-2019#convention-categories) analyzers are built into Visual Studio. The analyzer's diagnostic ID, or code format is IDExxxx, for example, IDE0067. You can configure preferences in the [text editor options page](../ide/code-styles-and-code-cleanup.md) or in an [EditorConfig file](/dotnet/fundamentals/code-analysis/code-style-rule-options). Starting in .NET 5.0, code style analyzers are included with the .NET SDK and can be strictly enforced as build warnings or errors. For more information, see [Overview of .NET source code analysis](/dotnet/fundamentals/productivity/code-analysis#code-style-analysis).
+- [Code style](/dotnet/fundamentals/code-analysis/code-style-rule-options?preserve-view=true&view=vs-2019#convention-categories) analyzers are built into Visual Studio. The analyzer's diagnostic ID, or code format is IDExxxx, for example, IDE0001. You can configure preferences in the [text editor options page](../ide/code-styles-and-code-cleanup.md) or in an [EditorConfig file](/dotnet/fundamentals/code-analysis/code-style-rule-options). Starting in .NET 5.0, code style analyzers are included with the .NET SDK and can be strictly enforced as build warnings or errors. For more information, see [Overview of .NET source code analysis](/dotnet/fundamentals/productivity/code-analysis#code-style-analysis).
 
 - [Code quality](/dotnet/fundamentals/code-analysis/quality-rules/index) analyzers are now included with the .NET 5 SDK and enabled by default. The analyzer's diagnostic ID, or code format is CAxxxx, for example, CA1822. For more information, see [Overview of .NET code quality analysis](/dotnet/fundamentals/productivity/code-analysis#code-quality-analysis).
 
@@ -103,4 +103,4 @@ You can't configure the severity of rules from analyzers that were installed as
 
 - [Analyzers FAQ](analyzers-faq.yml)
 - [Write your own code analyzer](../extensibility/getting-started-with-roslyn-analyzers.md)
-- [.NET Compiler Platform SDK](/dotnet/csharp/roslyn-sdk/)
+- [.NET Compiler Platform SDK](/dotnet/csharp/roslyn-sdk/)

docs/extensibility/roslyn-version-support.md

@@ -23,7 +23,7 @@ As an example, to ensure that your custom analyzer works on all versions of Visu
 
 | Roslyn package version | Minimum supported Visual Studio version |
 | - | - |
-| 4.3.0 | Visual Studio 2022 version 17.3 |
+| 4.3.1 | Visual Studio 2022 version 17.3 |
 | 4.2.0 | Visual Studio 2022 version 17.2 |
 | 4.1.0 | Visual Studio 2022 version 17.1 |
 | 4.0.1 | Visual Studio 2022 RTM |

docs/ide/file-nesting-solution-explorer.md

@@ -16,10 +16,10 @@ ms.technology: vs-ide-general
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-**Solution Explorer** nests related files to help organize them and make them easier to locate. For example, if you add a Windows Forms form to a project, the code file for the form is nested below the form in **Solution Explorer**. In ASP.NET Core projects, file nesting can be taken a step further. You can choose between the file nesting presets **Off**, **Default**, and **Web**. You can also [customize how files are nested](#customize-file-nesting) or [create solution-specific and project-specific settings](#create-project-specific-settings).
+**Solution Explorer** nests related files to help organize them and make them easier to locate. For example, if you add a Windows Forms form to a project, the code file for the form is nested below the form in **Solution Explorer**. In .NET Core (and .NET 5 and later) projects, file nesting can be taken a step further. You can choose between the file nesting presets **Off**, **Default**, and **Web**. You can also [customize how files are nested](#customize-file-nesting) or [create solution-specific and project-specific settings](#create-project-specific-settings).
 
 > [!NOTE]
-> Until Visual Studio 2022 version 17.3, this feature was only supported for ASP.NET Core projects.
+> In Visual Studio 2022 version 17.2 and earlier, this feature was only supported for ASP.NET Core projects.
 
 ## File nesting options
 

docs/ide/reference/options-text-editor-javascript-linting.md

@@ -2,7 +2,7 @@
 title: Options, Text Editor, JavaScript, Linting
 description: Learn how to use the Linting page of the Options dialog box to set options for analyzing code in the Code Editor.
 ms.custom: SEO-VS-2020
-ms.date: 1/15/2019
+ms.date: 9/30/2022
 ms.technology: vs-javascript
 ms.topic: reference
 f1_keywords:
@@ -20,7 +20,7 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-Use the **Linting** page of the **Options** dialog box to set options for analyzing code in the Code Editor. To access this page, on the menu bar, choose **Tools** > **Options**, and then expand **Text Editor** > **JavaScript/TypeScript** > **Linting**.
+Use the **Linting** page of the **Options** dialog box to set options for analyzing code in the Code Editor (note that you can override these options in some project types, like the [standalone React project templates](../../javascript/tutorial-create-react-app.md)). To access this page, on the menu bar, choose **Tools** > **Options**, and then expand **Text Editor** > **JavaScript/TypeScript** > **Linting**.
 
 ## ESLint Settings
 
@@ -31,12 +31,9 @@ These options let you enable static JavaScript and TypeSCript code analysis, and
 |Option|Description|
 |------------|-----------------|
 |**Enable ESLint**|When this option is selected, the Code Editor allows for static analysis on the code.|
-|**Lint all files included in project, even closed files**|When this option is selected, closed files are analyzed, unless diagnostics are only reported for open files.|
-
-## Global ESLint Config Options
-
-This option lets you copy the location of the global ESLint configuration file. Also, if you previously changed the location, you can reset the file to its default location.
+|**Lint *file extension* files**|These options allow you to configure which file extensions should be linted. For example, if "Lint TypeScript files" is selected, then documents with a *.ts* file extension will be linted.|
 
 ## See also
 
-- [General, Environment, Options Dialog Box](../../ide/reference/general-environment-options-dialog-box.md)
+- [Linting JavaScript in Visual Studio](../../javascript/linting-javascript.md)
+- [General, Environment, Options Dialog Box](../../ide/reference/general-environment-options-dialog-box.md)

docs/javascript/media/vs-2022/linting-project-properties.png

@@ -16,7 +16,7 @@ ms.workload:
 ---
 # MSBuild inline tasks with RoslynCodeTaskFactory
 
-Similar to the [CodeTaskFactory](../msbuild/msbuild-inline-tasks.md), RoslynCodeTaskFactory uses the cross-platform Roslyn compilers to generate in-memory task assemblies for use as inline tasks.  RoslynCodeTaskFactory tasks target .NET Standard and can work on .NET Framework and .NET Core runtimes as well as other platforms such as Linux and Mac OS.
+Similar to the [CodeTaskFactory](../msbuild/msbuild-inline-tasks.md), RoslynCodeTaskFactory uses the cross-platform Roslyn compilers to generate in-memory task assemblies for use as inline tasks.  RoslynCodeTaskFactory tasks target .NET Standard and can work on .NET Framework and .NET Core runtimes as well as other platforms such as Linux and macOS.
 
 >[!NOTE]
 >The RoslynCodeTaskFactory is available in MSBuild 15.8 and above only. MSBuild versions follow Visual Studio versions, so RoslynCodeTaskFactory is available in Visual Studio 2017 version 15.8 and higher.

docs/msbuild/msbuild-roslyncodetaskfactory.md

@@ -43,6 +43,6 @@ The following is a list of the VSTO Runtime releases and the corresponding versi
 | 10.0.60715 | 07/20/2015 | Microsoft Office 2016 |
 | 10.0.60724 | 07/24/2015 | Microsoft Office 2016 |
 | 10.0.60825 | 11/19/2016 | Microsoft Office 2016 |
-| 10.0.60828 | 01/12/2018 | Microsoft Office 2019 / <br>Office 365 |
+| 10.0.60828 | 01/12/2018 | Microsoft Office 2019 / <br>Office 365 / <br>Office 2021 |
 
 For more information on the Office Support Lifecycle please see [Lifecycle FAQ - Office, Office 365, and Microsoft 365](/lifecycle/faq/office).

docs/vsto/visual-studio-tools-for-office-runtime.md

@@ -1,6 +1,6 @@
 ---
 title: Visual Studio for Mac 8.10 and .NET on Apple Silicon machines
-description: Steps for getting supported versions of .NET working in 2019 on M1 machines.
+description: Steps for getting supported versions of .NET working in 2019 on Apple Silicon machines.
 author: jmatthiesen
 ms.author: jomatthi
 manager: dominicn
@@ -12,7 +12,7 @@ ms.assetid: db2dc420-63d2-44ef-bdda-a351561dc900
 
  [!INCLUDE [Visual Studio for Mac](~/includes/applies-to-version/vs-mac-only.md)]
 
-On Apple Silicon machines (also known as M1 or ARM), Visual Studio for Mac 8.10 does not support the .NET 6 Arm64 SDK. .NET 5 and .NET Core 3.1 x64 SDKs are supported. .NET 6 x64 SDK is required for building projects since the .NET 5 x64 and .NET Core 3.1 x64 SDKs are not supported for building on Apple Silicon machines.
+On Apple Silicon machines (also known as M1, M2, or ARM), Visual Studio for Mac 8.10 does not support the .NET 6 Arm64 SDK. .NET 5 and .NET Core 3.1 x64 SDKs are supported. .NET 6 x64 SDK is required for building projects since the .NET 5 x64 and .NET Core 3.1 x64 SDKs are not supported for building on Apple Silicon machines.
 
 .NET 6 is not fully supported by Visual Studio for Mac 8.10 since C# 10 is not supported in the editor. For this reason the New Project dialog will not show .NET 6.0 as an option when creating new projects.
 

mac/uninstall-net-2019.md

@@ -1,6 +1,6 @@
 ---
 title: Visual Studio for Mac 17.0 and .NET on Apple Silicon machines
-description: Steps for getting supported versions of .NET working in 2022 on M1 machines.
+description: Steps for getting supported versions of .NET working in 2022 on Apple Silicon machines.
 author: jmatthiesen
 ms.author: jomatthi
 manager: dominicn
@@ -12,7 +12,7 @@ ms.assetid: 18f722bc-3d9d-4c75-9e77-d66b64784c8d
 
  [!INCLUDE [Visual Studio for Mac](~/includes/applies-to-version/vs-mac-only.md)]
 
-On Apple Silicon machines (also known as M1 or ARM) with older x64 SDKs installed, you'll need to remove all existing .NET installations in order to use the .NET 6 GA Arm64 SDK.  
+On Apple Silicon machines (also known as M1, M2, or ARM) with older x64 SDKs installed, you'll need to remove all existing .NET installations in order to use the .NET 6 GA Arm64 SDK.  
 
 > [!NOTE]
 > This information is specific for Visual Studio for Mac 2022 Preview (17.0) versions. For information on this process for Visual Studio for Mac 2019 versions, see [Visual Studio for Mac 8.10 and .NET on Apple Silicon machines](/visualstudio/mac/uninstall-net-2019) for details.

mac/uninstall-net-2022.md

@@ -174,7 +174,7 @@ The Android SDK is required for development of Android applications. To complete
 > [!WARNING]
 > Note that Android signing keys that are generated by Visual Studio for Mac are located in `~/Library/Developer/Xamarin/Keystore`. Make sure to back these up appropriately, or avoid removing this directory if you wish to keep your keystore.
 
-The Java SDK (JDK) doesn't need to be uninstalled, as it's already pre-packaged as part of Mac OS X / macOS.
+The Java SDK (JDK) doesn't need to be uninstalled, as it's already pre-packaged as part of macOS.
 
 ### Uninstall Android AVD