Merge pull request #11012 from MicrosoftDocs/main638911370741931633sync_temp

Court72 · web-flow · commit 692d3f51da0d · 2025-08-18T14:27:43.000-06:00
Repo sync for protected branch
diff --git a/docs/code-quality/analyzers-faq.yml b/docs/code-quality/analyzers-faq.yml
@@ -1,7 +1,7 @@
 ### YamlMime:FAQ
 metadata:
   title: EditorConfig versus analyzers
-  ms.date: 10/05/2021
+  ms.date: 08/15/2025
   description: Learn about .NET Compiler Platform-based code analysis in Visual Studio. See answers to questions about EditorConfig files, rule sets, and other topics.
   ms.topic: faq
   helpviewer_keywords:
@@ -30,23 +30,25 @@ sections:
         answer: |
           Rule sets and EditorConfig files can coexist and can both be used to configure analyzers. Both EditorConfig files and rule sets let you enable and disable rules and set their severity.
 
-          However, EditorConfig files offer additional ways to configure rules too:
+          However, in Visual Studio 2019 version 16.5 and later, rule set files are deprecated in favor of EditorConfig files, and .NET Core and .NET 5+ projects don't support all the rule set menu commands. For more information, see [Convert an existing rule set file to an EditorConfig file](../code-quality/use-roslyn-analyzers.md#convert-an-existing-rule-set-file-to-an-editorconfig-file).
+
+          EditorConfig files offer additional ways to configure rules:
 
           - For the .NET code-quality analyzers, EditorConfig files let you [define which types of code to analyze](/dotnet/fundamentals/code-analysis/code-quality-rule-options).
-          - For the .NET code-style analyzers that are built into Visual Studio, EditorConfig files let you [define the preferred code styles](/dotnet/fundamentals/code-analysis/code-style-rule-options) for a codebase.
+          - For the .NET code-style analyzers and .NET code-quality analyzers, EditorConfig files let you [define the preferred code styles](/dotnet/fundamentals/code-analysis/code-style-rule-options) for a codebase.
 
           In addition to rule sets and EditorConfig files, some analyzers are configured through the use of text files marked as [additional files](../ide/build-actions.md#build-action-values) for the C# and VB compilers.
 
           > [!NOTE]
           > - EditorConfig files can only be used to enable rules and set their severity in Visual Studio 2019 version 16.3 and later.
-          > - EditorConfig files cannot be used to configure legacy analysis, whereas rule sets can.
+          > - EditorConfig files can't be used to configure legacy analysis, whereas rule sets can.
 
   - name: Code analysis in continuous integration (CI) builds
     questions:
       - question: |
           Does .NET Compiler Platform-based code analysis work in continuous integration (CI) builds?
         answer: |
-          Yes. For analyzers that are installed from a NuGet package, those rules are [enforced at build time](roslyn-analyzers-overview.md#build-errors), including during a CI build. Analyzers used in CI builds respect rule configuration from both rule sets and EditorConfig files. Currently, the code analyzers that are built into Visual Studio are not available as a NuGet package, and so these rules are not enforceable in a CI build.
+          Yes. For analyzers that are installed with .NET SDK 5.0 or higher, or from a NuGet package, those rules are [enforced at build time](roslyn-analyzers-overview.md#build-errors), including during a CI build. Analyzers used in CI builds respect rule configuration from both rule sets and EditorConfig files. Starting with .NET 5.0, the code style analyzers that are built into Visual Studio are also included in the .NET SDK, and most of them are enforceable in a CI build. For more information, see [Enable on build](/dotnet/fundamentals/code-analysis/overview?tabs=net-9#enable-on-build).
 
   - name: IDE analyzers versus StyleCop
     questions:
@@ -69,7 +71,7 @@ sections:
       - question: |
           What's the difference between FxCop analyzers and .NET analyzers?
         answer: |
-          Both FxCop analyzers and .NET analyzers refers to the .NET Compiler Platform ("Roslyn") analyzer implementations of FxCop CA rules. Prior to Visual Studio 2019 16.8 and .NET 5.0, these analyzers shipped as `Microsoft.CodeAnalysis.FxCopAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers). Starting in Visual Studio 2019 16.8 and .NET 5.0, these analyzers are [included with the .NET SDK](/dotnet/fundamentals/code-analysis/overview). They are also available as `Microsoft.CodeAnalysis.NetAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers). Please consider [migrating from FxCop analyzers to .NET analyzers](migrate-from-fxcop-analyzers-to-net-analyzers.md).
+          Both FxCop analyzers and .NET analyzers refers to the .NET Compiler Platform ("Roslyn") analyzer implementations of FxCop CA rules. Prior to Visual Studio 2019 16.8 and .NET 5.0, these analyzers shipped as `Microsoft.CodeAnalysis.FxCopAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers). Starting in Visual Studio 2019 16.8 and .NET 5.0, these analyzers are [included with the .NET SDK](/dotnet/fundamentals/code-analysis/overview). They're also available as `Microsoft.CodeAnalysis.NetAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers). Please consider [migrating from FxCop analyzers to .NET analyzers](migrate-from-fxcop-analyzers-to-net-analyzers.md).
 
   - name: Treat warnings as errors
     questions:
diff --git a/docs/code-quality/in-source-suppression-overview.md b/docs/code-quality/in-source-suppression-overview.md
@@ -194,7 +194,7 @@ The properties of the attribute include:
 
   - [`module`](#module-suppression-scope): This scope suppresses warnings against an assembly. It's a global suppression that applies to the entire project.
 
-  - `resource`: ([Legacy FxCop](../code-quality/static-code-analysis-for-managed-code-overview.md) only) This scope suppresses warnings in diagnostic info written to resource files that are part of the module (assembly). This scope isn't read or respected in C#/VB compilers for Roslyn analyzer diagnostics, which only analyze source files.
+  - `resource`: ([legacy analysis](../code-quality/static-code-analysis-for-managed-code-overview.md) only) This scope suppresses warnings in diagnostic info written to resource files that are part of the module (assembly). This scope isn't read or respected in C#/VB compilers for Roslyn analyzer diagnostics, which only analyze source files.
 
   - `type`: This scope suppresses warnings against a type.
 
@@ -222,7 +222,7 @@ If there are strict performance reasons for minimizing in-source suppression met
 
 For maintainability reasons, omitting the rule name isn't recommended.
 
-### Suppress selective violations within a method body
+### Suppress selective violations within a method body (legacy analysis only)
 
 Suppression attributes can be applied to a method, but can't be embedded within a method body. All violations of a particular rule are suppressed if you add the <xref:System.Diagnostics.CodeAnalysis.SuppressMessageAttribute> attribute to the method.
 
diff --git a/docs/code-quality/roslyn-analyzers-overview.md b/docs/code-quality/roslyn-analyzers-overview.md
@@ -73,7 +73,7 @@ Visual Studio includes a core set of Roslyn analyzers, which are always active.
 
 ### Scope
 
-If you install an analyzer as a NuGet package, the preferred method, it applies only to the project where the NuGet package is installed. Otherwise, if you install an analyzer as a Visual Studio extension, it applies at the solution level and to all instances of Visual Studio. In team environments, an analyzer you install as a NuGet package is in scope for all developers that work on that project.
+If you install an analyzer as a NuGet package, the preferred method for external analyzers, it applies only to the project where the NuGet package is installed. Otherwise, if you install an analyzer as a Visual Studio extension, it applies at the solution level and to all instances of Visual Studio. In team environments, an analyzer you install as a NuGet package is in scope for all developers that work on that project.
 
 > [!NOTE]
 > First-party analyzers ship within the .NET SDK. It's preferable that you enable these analyzers from the .NET SDK instead of installing them as a `Microsoft.CodeAnalysis.NetAnalyzers` [NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.NetAnalyzers). Enabling the analyzers from the .NET SDK ensures that you automatically get analyzer bug fixes and new analyzers as soon as you update the SDK. For more information about analyzers, see [Enable or install first-party .NET analyzers](install-net-analyzers.md).
@@ -92,7 +92,7 @@ The following screenshot shows the command-line build output from building a pro
 
 ### Rule severity
 
-If you want to configure [analyzer rule severity](../code-quality/use-roslyn-analyzers.md#configure-severity-levels), you must install the analyzer as a NuGet package. You can't configure rule severity from analyzers that were installed as a Visual Studio extension.
+If you want to configure [analyzer rule severity](../code-quality/use-roslyn-analyzers.md#configure-severity-levels) for external analyzers, you must install the analyzer as a NuGet package. You can't configure rule severity from analyzers that were installed as a Visual Studio extension.
 
 ## Next steps
 
diff --git a/docs/ide/reference/media/vs-2022/remove-unused-references-command.png b/docs/ide/reference/media/vs-2022/remove-unused-references-command.png
diff --git a/docs/ide/reference/media/vs-2022/remove-unused-references-dialog.png b/docs/ide/reference/media/vs-2022/remove-unused-references-dialog.png
diff --git a/docs/ide/reference/remove-unused-references.md b/docs/ide/reference/remove-unused-references.md
@@ -1,7 +1,7 @@
 ---
 title: Remove unused references
 description: Learn how to clean up project references and NuGet packages that have no usage with the new Remove Unused References command.
-ms.date: 3/6/2024
+ms.date: 8/15/2025
 ms.topic: reference
 author: mikadumont
 ms.author: midumont
@@ -31,20 +31,30 @@ This refactoring applies to:
 
 1. Verify that the option is enabled.
 
-   Select **Tools** > **Options** > **Text Editor** > **C#** > **Advanced**, and enable **Show "Removed Unused References" command in Solution Explorer (experimental)**.
+   Select **Tools** > **Options** > **Text Editor** > **C#** > **Advanced**, and enable **Show "Removed Unused References" command in Solution Explorer**.
 
-1. Right click on a project name or dependencies node in Solution Explorer.
+1. In Solution Explorer, right click on a project name or the **Dependencies** node.
 
 1. Select **Remove Unused References**.
 
-    ![Remove Unused References command](media/remove-unused-references-command.png)
+   ::: moniker range=">= vs-2022"
+   ![Screenshot of Remove Unused References command.](media/vs-2022/remove-unused-references-command.png)
+   ::: moniker-end
+   ::: moniker range="vs-2019"
+   ![Screenshot of Remove Unused References command.](media/remove-unused-references-command.png)
+   ::: moniker-end
 
-1. The **Remove Unused References** dialog will open displaying references that have no usage in source code. Unused references will be pre-selected for removal with an option to preserve references by selecting `Keep` from the Action drop down.
+1. The **Remove Unused References** dialog opens, displaying references that have no usage in source code. Unused references are pre-selected for removal with an option to preserve references by selecting `Keep` from the Action drop down.
 
-    ![Remove Unused References dialog](media/remove-unused-references-dialog.png)
+   ::: moniker range=">= vs-2022"
+   ![Screenshot of Remove Unused References dialog.](media/vs-2022/remove-unused-references-dialog.png)
+   ::: moniker-end
+   ::: moniker range="vs-2019"
+   ![Screenshot of Remove Unused References dialog.](media/remove-unused-references-dialog.png)
+   ::: moniker-end
 
 1. Click `Apply` to remove selected references.
 
 ## See also
 
-- [Refactoring](../refactoring-in-visual-studio.md)
+- [Refactoring](../refactoring-in-visual-studio.md)
diff --git a/docs/xaml-tools/xaml-overview.md b/docs/xaml-tools/xaml-overview.md
@@ -1,7 +1,7 @@
 ---
 title: Use the XAML code editor and XAML Designer tools
 description: Get basic information about the Extensible Application Markup Language (XAML) and how to work with the XAML code editor and XAML Designer tools in Visual Studio.
-ms.date: 06/23/2020
+ms.date: 08/15/2025
 ms.topic: overview
 author: maddymontaquila
 ms.author: maleger
@@ -13,9 +13,10 @@ ms.subservice: xaml-tools
 Extensible Application Markup Language (XAML) is a declarative language that's based on XML. XAML is used extensively in the following types of applications to build user interfaces:
 
 - [Windows Presentation Foundation (WPF) apps](/dotnet/framework/wpf/advanced/xaml-in-wpf)
-- [Universal Windows Platform (UWP) apps](/windows/uwp/xaml-platform/xaml-overview)
-- [Xamarin.Forms apps](/xamarin/xamarin-forms/xaml/)
 - [.NET MAUI apps](/dotnet/maui/xaml)
+- [WinUI](/windows/apps/winui/winui3/)
+- [Universal Windows Platform (UWP) apps](/windows/uwp/xaml-platform/xaml-overview)
+- [Xamarin.Forms apps](/xamarin/xamarin-forms/xaml/) (unsupported)
 
 The following XAML code defines a simple button control.
 
