Merged main into live

Author: mijacobs

.openpublishing.redirection.json

@@ -20684,7 +20684,7 @@
     },
     {
       "source_path": "docs/debugger/specify-command-line-arguments.md",
-      "redirect_url": "../../visualstudio/debugger/project-settings-for-a-cpp-debug-configuration",
+      "redirect_url": "/visualstudio/debugger/project-settings-for-a-cpp-debug-configuration",
       "redirect_document_id": false
     }
   ]

docs/code-quality/disable-code-analysis.md

@@ -24,7 +24,7 @@ Visual Studio allows you to control whether source code analyzers run at build t
 
 - Source analysis versus legacy analysis
 
-  This article applies to source code analysis and not to legacy (binary) analysis. For information about disabling legacy analysis, see [Enable and disable binary code analysis for managed code](how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md).
+  This article applies to source code analysis and not to legacy (binary) analysis. For information about disabling legacy analysis, see [Enable and disable binary code analysis for managed code](/previous-versions/visualstudio/visual-studio-2019/code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code).
 
 ## .NET Core, .NET Standard, and .NET 5+ projects
 
@@ -75,7 +75,7 @@ This page lets you disable code analysis in Visual Studio. There are limitations
 
 - Source analysis versus legacy analysis
 
-  This article applies to source code analysis and not to legacy (binary) analysis. For information about disabling legacy analysis, see [Enable and disable binary code analysis for managed code](how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md).
+  This article applies to source code analysis and not to legacy (binary) analysis. For information about disabling legacy analysis, see [Enable and disable binary code analysis for managed code](/previous-versions/visualstudio/visual-studio-2019/code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code).
 
 ## .NET Core, .NET Standard, and .NET 5+ projects
 
@@ -114,4 +114,4 @@ For example:
 ## Related content
 
 - [Suppress code analysis violations](in-source-suppression-overview.md)
-- [Enable and disable binary code analysis for managed code](how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md)
+- [Enable and disable binary code analysis for managed code](/previous-versions/visualstudio/visual-studio-2019/code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code)

docs/code-quality/how-to-run-code-analysis-manually-for-managed-code.md

@@ -37,4 +37,4 @@ To manually run a code analysis, follow these steps:
 ## Related content
 
 - [Disable source code analysis for .NET](disable-code-analysis.md)
-- [Enable and disable binary code analysis for managed code](how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md)
+- [Enable and disable binary code analysis for managed code](/previous-versions/visualstudio/visual-studio-2019/code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code)

docs/code-quality/in-source-suppression-overview.md

@@ -226,9 +226,9 @@ For maintainability reasons, omitting the rule name isn't recommended.
 
 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.
 
-In some cases, you might want to suppress a particular instance of the violation. Consider the example where future code isn't automatically exempt from the code analysis rule. Certain code analysis rules allow you to suppress a particular instance of the violation by using the `MessageId` property of the `SuppressMessageAttribute` attribute. In general, legacy rules for violations on a particular symbol (a local variable or parameter) respect the `MessageId` property. [CA1500:VariableNamesShouldNotMatchFieldNames](../code-quality/ca1500.md) is an example of such a rule. However, legacy rules for violations on executable code (non-symbol) don't respect the `MessageId` property. Also, .NET Compiler Platform ("Roslyn") analyzers don't respect the `MessageId` property.
+In some cases, you might want to suppress a particular instance of the violation. Consider the example where future code isn't automatically exempt from the code analysis rule. Certain code analysis rules allow you to suppress a particular instance of the violation by using the `MessageId` property of the `SuppressMessageAttribute` attribute. In general, legacy rules for violations on a particular symbol (a local variable or parameter) respect the `MessageId` property. [CA1500:VariableNamesShouldNotMatchFieldNames](/previous-versions/visualstudio/visual-studio-2019/code-quality/ca1500) is an example of such a rule. However, legacy rules for violations on executable code (non-symbol) don't respect the `MessageId` property. Also, .NET Compiler Platform ("Roslyn") analyzers don't respect the `MessageId` property.
 
-To suppress a particular symbol violation of a rule, specify the symbol name for the `MessageId` property of the `SuppressMessageAttribute` attribute. The following example shows code with two violations of [CA1500:VariableNamesShouldNotMatchFieldNames](../code-quality/ca1500.md): one violation for the `name` variable and another violation for the `age` variable. Only the violation for the `age` symbol is suppressed.
+To suppress a particular symbol violation of a rule, specify the symbol name for the `MessageId` property of the `SuppressMessageAttribute` attribute. The following example shows code with two violations of [CA1500:VariableNamesShouldNotMatchFieldNames](/previous-versions/visualstudio/visual-studio-2019/code-quality/ca1500): one violation for the `name` variable and another violation for the `age` variable. Only the violation for the `age` symbol is suppressed.
 
 ### [C#](#tab/csharp)
 
@@ -305,7 +305,7 @@ Managed code compilers and some external tools generate code to help rapid code
 
 For source code analysis, you can suppress messages in generated code in an *.editorconfig* file. For more information, see [Exclude generated code](/dotnet/fundamentals/code-analysis/configuration-options#exclude-generated-code).
 
-For legacy code analysis, you can choose whether to suppress code analysis warnings and errors for generated code. For information about how to suppress such warnings and errors, see [Suppress code analysis warnings for generated code](../code-quality/how-to-suppress-code-analysis-warnings-for-generated-code.md).
+For legacy code analysis, you can choose whether to suppress code analysis warnings and errors for generated code. For information about how to suppress such warnings and errors, see [Suppress code analysis warnings for generated code](/previous-versions/visualstudio/visual-studio-2019/code-quality/how-to-suppress-code-analysis-warnings-for-generated-code).
 
 > [!NOTE]
 > Code analysis ignores `GeneratedCodeAttribute` when it is applied to either an entire assembly or a single parameter.

docs/code-quality/migrate-from-fxcop-analyzers-to-net-analyzers.md

@@ -17,7 +17,7 @@ ms.subservice: code-analysis
 
 # Migrate from NuGet FxCop analyzers to .NET analyzers
 
-Source analysis by .NET Compiler Platform ("Roslyn") analyzers replaces [legacy analysis](code-analysis-for-managed-code-overview.md) for managed code. Many of the legacy analysis (FxCop) rules have already been rewritten as source analyzers.
+Source analysis by .NET Compiler Platform ("Roslyn") analyzers replaces [legacy analysis](/previous-versions/visualstudio/visual-studio-2019/code-quality/code-analysis-for-managed-code-overview) for managed code. Many of the legacy analysis (FxCop) rules have already been rewritten as source analyzers.
 
 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).
 

docs/code-quality/migrate-from-legacy-analysis-to-net-analyzers.md

@@ -17,7 +17,7 @@ ms.subservice: code-analysis
 
 # Migrate from legacy analysis (FxCop) to source analysis (.NET analyzers)
 
-Source analysis by .NET Compiler Platform ("Roslyn") analyzers replaces [legacy analysis](../code-quality/code-analysis-for-managed-code-overview.md) for managed code. For newer project templates such as .NET Core and .NET Standard projects, legacy analysis is not available.
+Source analysis by .NET Compiler Platform ("Roslyn") analyzers replaces [legacy analysis](/previous-versions/visualstudio/visual-studio-2019/code-quality/code-analysis-for-managed-code-overview) for managed code. For newer project templates such as .NET Core and .NET Standard projects, legacy analysis is not available.
 
 Many of the legacy analysis (FxCop) rules have already been rewritten for .NET analyzers, a set of Roslyn code analyzers. Roslyn analyzers run source-code based analysis during compiler execution. Analyzer results are reported along with compiler results.
 
@@ -31,7 +31,7 @@ For more information on the differences between legacy analysis and source analy
 
 To migrate to source analysis:
 
-1. [Enable or install the .NET analyzers](install-net-analyzers.md). Like legacy analysis rule violations, source code analysis violations appear in the Error List window in Visual Studio. In addition, source code analysis violations also show up in the code editor as *squiggles* under the offending code. The color of the squiggle depends on the [severity setting](../code-quality/use-roslyn-analyzers.md#configure-severity-levels) of the rule. To see the status of rules ported to the new .NET analyzers, see [Ported and unported rules](../code-quality/fxcop-rule-port-status.md).
+1. [Enable or install the .NET analyzers](install-net-analyzers.md). Like legacy analysis rule violations, source code analysis violations appear in the Error List window in Visual Studio. In addition, source code analysis violations also show up in the code editor as *squiggles* under the offending code. The color of the squiggle depends on the [severity setting](../code-quality/use-roslyn-analyzers.md#configure-severity-levels) of the rule. To see the status of rules ported to the new .NET analyzers, see [Ported and unported rules](/previous-versions/visualstudio/visual-studio-2019/code-quality/fxcop-rule-port-status).
 
    > [!NOTE]
    > 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). For more information, see [Migrate from FxCop analyzers to .NET analyzers](migrate-from-fxcop-analyzers-to-net-analyzers.md).

docs/code-quality/static-code-analysis-for-managed-code-overview.md

@@ -27,7 +27,7 @@ The analysis tool represents the checks it performs during an analysis as warnin
 
 You can run code analysis on your project manually or automatically.
 
-To run code analysis each time that you build a project, select the option on the project's **Code Analysis** property page. For more information, see [How to: Enable and Disable Automatic Code Analysis](../code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md).
+To run code analysis each time that you build a project, select the option on the project's **Code Analysis** property page. For more information, see [How to: Enable and Disable Automatic Code Analysis](/previous-versions/visualstudio/visual-studio-2019/code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code).
 
 To run code analysis manually on a project, from the menu bar choose **Analyze** > **Run Code Analysis** > **Run Code Analysis on \<project>**.
 
@@ -72,4 +72,4 @@ You can use the integrated features of the build system to run the analysis tool
 
 - [Overview of .NET Compiler Platform-based analyzers](../code-quality/roslyn-analyzers-overview.md)
 - [Using Rule Sets to Group Code Analysis Rules](/previous-versions/visualstudio/visual-studio-2019/code-quality/using-rule-sets-to-group-code-analysis-rules)
-- [How to: Enable and Disable Automatic Code Analysis](../code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code.md)
+- [How to: Enable and Disable Automatic Code Analysis](/previous-versions/visualstudio/visual-studio-2019/code-quality/how-to-enable-and-disable-automatic-code-analysis-for-managed-code)

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

@@ -390,6 +390,6 @@ In a .NET Core project, if you add a reference to a project that has NuGet analy
 
 - [Overview of code analyzers in Visual Studio](../code-quality/roslyn-analyzers-overview.md)
 - [Submit a code analyzer bug](https://github.com/dotnet/roslyn-analyzers/issues)
-- [Use rule sets](../code-quality/using-rule-sets-to-group-code-analysis-rules.md)
+- [Use rule sets](/previous-versions/visualstudio/visual-studio-2019/code-quality/using-rule-sets-to-group-code-analysis-rules)
 - [Suppress code analysis violations](../code-quality/in-source-suppression-overview.md)
 - [Configuration options for code analysis](/dotnet/fundamentals/code-analysis/configuration-options)

docs/debugger/assertions-in-managed-code.md

@@ -272,4 +272,4 @@ You can set assertions in your program configuration file as well as in your cod
 - [Tracing and Instrumenting Applications](/dotnet/framework/debug-trace-profile/tracing-and-instrumenting-applications)
 - [How to: Compile Conditionally with Trace and Debug](/dotnet/framework/debug-trace-profile/how-to-compile-conditionally-with-trace-and-debug)
 - [Managed debugging: Recommended project settings](../debugger/managed-debugging-recommended-property-settings.md)
-- [Debugging Managed Code](../debugger/debugging-managed-code.md)
+- [Debugging Managed Code](/visualstudio/debugger/)

docs/debugger/com-server-and-container-debugging.md

@@ -52,4 +52,4 @@ To access the *Project* Property Pages dialog box, right-click your project in S
 
 ## Related content
 
-- [COM and ActiveX Debugging](../debugger/com-and-activex-debugging.md)
+- [COM and ActiveX Debugging](/previous-versions/visualstudio/visual-studio-2017/debugger/com-and-activex-debugging)