Merge pull request #10 from MicrosoftDocs/master

bringing up to date

Author: heiligerdankgesang

.openpublishing.redirection.json

@@ -41985,9 +41985,24 @@
       "redirect_url": "/dotnet/fundamentals/code-analysis/code-quality-rule-options",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/code-quality/install-fxcop-analyzers.md",
+      "redirect_url": "/visualstudio/code-quality/install-net-analyzers",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/code-quality/fxcop-analyzers.yml",
-      "redirect_url": "/visualstudio/code-quality/migrate-from-legacy-analysis-to-fxcop-analyzers",
+      "redirect_url": "/visualstudio/code-quality/migrate-from-legacy-analysis-to-net-analyzers",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/code-quality/fxcop-analyzers-faq.md",
+      "redirect_url": "/visualstudio/code-quality/net-analyzers-faq",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/code-quality/migrate-from-legacy-analysis-to-fxcop-analyzers.md",
+      "redirect_url": "/visualstudio/code-quality/migrate-from-legacy-analysis-to-net-analyzers",
       "redirect_document_id": false
     },
     {

docs/code-quality/analyzers-faq.md

@@ -57,7 +57,13 @@ In addition to rule sets and EditorConfig files, some analyzers are configured t
 
 **Q**: What's the difference between legacy analysis and .NET Compiler Platform-based code analysis?
 
-**A**: .NET Compiler Platform-based code analysis analyzes source code in real time and during compilation, whereas legacy analysis analyzes binary files after build has completed. For more information, see [.NET Compiler Platform-based analysis versus legacy analysis](../code-quality/fxcop-analyzers-faq.md#whats-the-difference-between-legacy-fxcop-and-fxcop-analyzers).
+**A**: .NET Compiler Platform-based code analysis analyzes source code in real time and during compilation, whereas legacy analysis analyzes binary files after build has completed. For more information, see [.NET Compiler Platform-based analysis versus legacy analysis](../code-quality/net-analyzers-faq.md#whats-the-difference-between-legacy-fxcop-and-net-analyzers).
+
+## FxCop analyzers versus .NET analyzers
+
+**Q**: What's the difference between FxCop analyzers and .NET analyzers?
+
+**A**: 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).
 
 ## Treat warnings as errors
 
@@ -75,12 +81,12 @@ In addition to rule sets and EditorConfig files, some analyzers are configured t
      </Project>
      ```
 
-  2. Add a line to your .csproj or .vbproj project file to import the .props file you created in the previous step. This line must be placed before any lines that import the FxCop analyzer .props files. For example, if your .props file is named codeanalysis.props:
+  2. Add a line to your .csproj or .vbproj project file to import the .props file you created in the previous step. This line must be placed before any lines that import the analyzer .props files. For example, if your .props file is named codeanalysis.props:
 
      ```xml
      ...
      <Import Project="..\..\codeanalysis.props" Condition="Exists('..\..\codeanalysis.props')" />
-     <Import Project="..\packages\Microsoft.CodeAnalysis.FxCopAnalyzers.2.6.5\build\Microsoft.CodeAnalysis.FxCopAnalyzers.props" Condition="Exists('..\packages\Microsoft.CodeAnalysis.FxCopAnalyzers.2.6.5\build\Microsoft.CodeAnalysis.FxCopAnalyzers.props')" />
+     <Import Project="..\packages\Microsoft.CodeAnalysis.NetAnalyzers.5.0.0\build\Microsoft.CodeAnalysis.NetAnalyzers.props" Condition="Exists('..\packages\Microsoft.CodeAnalysis.NetAnalyzers.5.0.0\build\Microsoft.CodeAnalysis.NetAnalyzers.props')" />
      ...
      ```
 

docs/code-quality/fxcop-analyzers-faq.md

@@ -1,12 +1,12 @@
 ---
 title: FxCop rule port status
 ms.date: 05/21/2019
-description: Learn about the static code analysis rules that have been ported to FxCop analyzers in Visual Studio. View ported rules and resources on porting updates.
+description: Learn about the static code analysis rules that have been ported to .NET analyzers in Visual Studio. View ported rules and resources on porting updates.
 ms.custom: SEO-VS-2020
 ms.topic: reference
 helpviewer_keywords:
 - fxcop rules
-- fxcop analyzers, ported rules
+- .NET analyzers, ported rules
 author: mikejo5000
 ms.author: mikejo
 manager: jillfra
@@ -15,13 +15,13 @@ ms.workload:
 ---
 # Fxcop rule port status
 
-If you previously used static code analysis in Visual Studio, you may be wondering which of those rules are available in the current implementation as [FxCop analyzers](install-fxcop-analyzers.md). This page lists the rules that have been ported. See [Unported rules](fxcop-unported-rules.md) for those that haven't been ported and whether there are plans to port them.
+If you previously used static code analysis in Visual Studio, you may be wondering which of those rules are available in the current implementation as [.NET analyzers](install-net-analyzers.md). This page lists the rules that have been ported. See [Unported rules](fxcop-unported-rules.md) for those that haven't been ported and whether there are plans to port them.
 
 ## Ported rules
 
-The [autogenerated documentation page](https://github.com/dotnet/roslyn-analyzers/blob/master/src/Microsoft.CodeAnalysis.FxCopAnalyzers/Microsoft.CodeAnalysis.FxCopAnalyzers.md) in the roslyn-analyzers repo has the most up-to-date list of rules that have been ported to FxCop analyzers. That page also has additional information, such as whether the rule is enabled by default and if it has an associated *code fix*. ([Code fixes](../ide/quick-actions.md) are one-click fixes available in the light bulb icon menu in Visual Studio.)
+The [autogenerated documentation page](https://github.com/dotnet/roslyn-analyzers/blob/master/src/NetAnalyzers/Microsoft.CodeAnalysis.NetAnalyzers.md) in the roslyn-analyzers repo has the most up-to-date list of rules that have been ported to Roslyn analyzers. That page also has additional information, such as whether the rule is enabled by default and if it has an associated *code fix*. ([Code fixes](../ide/quick-actions.md) are one-click fixes available in the light bulb icon menu in Visual Studio.)
 
-As of the date on this page, the list of FxCop rules that have been ported to [FxCop analyzers](install-fxcop-analyzers.md) includes:
+As of the date on this page, the list of FxCop rules that have been ported to [.NET analyzers](install-net-analyzers.md) includes:
 
 Rule ID | Title
 --------|---------
@@ -58,7 +58,7 @@ Rule ID | Title
 [CA1050](/dotnet/fundamentals/code-analysis/quality-rules/ca1050) | Declare types in namespaces
 [CA1051](/dotnet/fundamentals/code-analysis/quality-rules/ca1051) | Do not declare visible instance fields
 [CA1052](/dotnet/fundamentals/code-analysis/quality-rules/ca1052) | Static holder types should be static or NotInheritable
-[CA1053](/dotnet/fundamentals/code-analysis/quality-rules/ca1053) | Static holder types should not have constructors (CA1053 is part of [CA1052](/dotnet/fundamentals/code-analysis/quality-rules/ca1052) for FxCop analyzers)
+[CA1053](/dotnet/fundamentals/code-analysis/quality-rules/ca1053) | Static holder types should not have constructors (CA1053 is part of [CA1052](/dotnet/fundamentals/code-analysis/quality-rules/ca1052) for .NET analyzers)
 [CA1054](/dotnet/fundamentals/code-analysis/quality-rules/ca1054) | Uri parameters should not be strings
 [CA1055](/dotnet/fundamentals/code-analysis/quality-rules/ca1055) | Uri return values should not be strings
 [CA1056](/dotnet/fundamentals/code-analysis/quality-rules/ca1056) | Uri properties should not be strings
@@ -198,4 +198,4 @@ CA9999 | Analyzer version mismatch
 
 ## See also
 
-- [Microsoft.CodeAnalysis.FxCopAnalyzers rules](https://github.com/dotnet/roslyn-analyzers/blob/master/src/Microsoft.CodeAnalysis.FxCopAnalyzers/Microsoft.CodeAnalysis.FxCopAnalyzers.md)
+- [.NET analyzer rules](https://github.com/dotnet/roslyn-analyzers/blob/master/src/NetAnalyzers/Microsoft.CodeAnalysis.NetAnalyzers.md)

docs/code-quality/fxcop-rule-port-status.md

@@ -4,7 +4,7 @@ ms.date: 05/21/2019
 ms.topic: reference
 helpviewer_keywords:
 - fxcop rules
-- fxcop analyzers, ported rules, unported rules, deprecated rules
+- .NET analyzers, ported rules, unported rules, deprecated rules
 author: mikejo5000
 ms.author: mikejo
 manager: jillfra

docs/code-quality/fxcop-unported-deprecated-rules.md

@@ -4,7 +4,7 @@ ms.date: 05/21/2019
 ms.topic: reference
 helpviewer_keywords:
 - fxcop rules
-- fxcop analyzers, ported rules, unported rules, rules that may be ported
+- .NET analyzers, ported rules, unported rules, rules that may be ported
 author: mikejo5000
 ms.author: mikejo
 manager: jillfra

docs/code-quality/fxcop-unported-rules-may-get-ported.md

@@ -4,7 +4,7 @@ ms.date: 05/21/2019
 ms.topic: reference
 helpviewer_keywords:
 - fxcop rules
-- fxcop analyzers, ported rules
+- .NET analyzers, ported rules
 author: mikejo5000
 ms.author: mikejo
 manager: jillfra