Merged main into live

Author: mijacobs

docs/ide/advanced-feature-overview.md

@@ -123,7 +123,7 @@ For more information about debugging in Visual Studio, see [First look at the de
 
 To improve app performance, check out the Visual Studio [profiling](../profiling/profiling-feature-tour.md) feature.
 
-Visual Studio offers [testing](../test/improve-code-quality.md) options like unit testing, Live Unit Testing, IntelliTest, and load and performance testing. Visual Studio also has advanced [code analysis](../code-quality/code-analysis-for-managed-code-overview.md) capabilities to find design, security, and other flaws.
+Visual Studio offers [testing](../test/improve-code-quality.md) options like unit testing, Live Unit Testing, IntelliTest, and load and performance testing. Visual Studio also has advanced [code analysis](/previous-versions/visualstudio/visual-studio-2019/code-quality/code-analysis-for-managed-code-overview) capabilities to find design, security, and other flaws.
 
 ## Deploy your finished application
 

docs/ide/build-actions.md

@@ -26,7 +26,7 @@ Some of the more common build actions for C# and Visual Basic project files are:
 |-|-|
 | **AdditionalFiles** | C#, Visual Basic | A non-source text file that's passed to the C# or Visual Basic compiler as input. This build action is mainly used to provide inputs to [analyzers](../code-quality/roslyn-analyzers-overview.md) that are referenced by a project to verify code quality. For more information, see [Use additional files](https://github.com/dotnet/roslyn/blob/main/docs/analyzers/Using%20Additional%20Files.md).|
 | **ApplicationDefinition** | WPF | The file that defines your application. When you first create a project, this file is *App.xaml*. |
-| **CodeAnalysisDictionary** | .NET | A custom word dictionary, used by Code Analysis for spell checking. See [How to: Customize the Code Analysis Dictionary](../code-quality/how-to-customize-the-code-analysis-dictionary.md)|
+| **CodeAnalysisDictionary** | .NET | A custom word dictionary, used by Code Analysis for spell checking. See [How to: Customize the Code Analysis Dictionary](/previous-versions/visualstudio/visual-studio-2019/code-quality/how-to-customize-the-code-analysis-dictionary)|
 | **Compile** | any | The file is passed to the compiler as a source file.|
 | **Content** | .NET | A file marked as **Content** can be retrieved as a stream by calling <xref:System.Windows.Application.GetContentStream%2A?displayProperty=nameWithType>. For ASP.NET projects, these files are included as part of the site when you deploy.|
 | **DesignData** | WPF | Used for XAML viewmodel files, to enable user controls to be viewed at design time, with dummy types and sample data. |

docs/ide/create-a-visual-basic-winform-in-visual-studio.md

@@ -156,7 +156,7 @@ Your application is ready to build and run.
 To learn more about Windows Forms, continue with the following tutorial:
 
 > [!div class="nextstepaction"]
-> [Tutorial: Create a picture viewer](tutorial-windows-forms-picture-viewer-layout.md)
+> [Tutorial: Create a picture viewer](/visualstudio/get-started/csharp/tutorial-windows-forms-picture-viewer-layout)
 
 Or try these other tutorials:
 

docs/ide/create-csharp-winform-visual-studio.md

@@ -226,7 +226,7 @@ After you add a button control to create an action, add a label control to recei
 Congratulations on completing this tutorial. To learn more, continue with the following tutorial:
 
 > [!div class="nextstepaction"]
-> [Tutorial: Create a picture viewer](tutorial-windows-forms-picture-viewer-layout.md)
+> [Tutorial: Create a picture viewer](/visualstudio/get-started/csharp/tutorial-windows-forms-picture-viewer-layout)
 
 Or try these other tutorials:
 

docs/ide/customizing-project-and-item-templates.md

@@ -36,7 +36,7 @@ For example, you can perform the following tasks:
 ## Related content
 
 - [Creating project and item templates](../ide/creating-project-and-item-templates.md)
-- [How to: Troubleshoot templates](../ide/how-to-troubleshoot-templates.md)
+- [How to: Troubleshoot templates](/troubleshoot/developer/visualstudio/project-build/how-to-troubleshoot-templates)
 - [How to: Create project templates](../ide/how-to-create-project-templates.md)
 - [How to: Create item templates](../ide/how-to-create-item-templates.md)
 - [Visual Studio template schema reference](../extensibility/visual-studio-template-schema-reference.md)

docs/ide/developer-community-guidelines.md

@@ -94,7 +94,7 @@ When we can't answer "yes" to any of these questions, we'll close it. But often
 
 If a suggestion doesn’t match our overall product direction, we will close it as *Out of Scope*. For example, we may have similar investments in other members of the Visual Studio family of products. Or the feature suggested might only be relevant to a few people, making an extension better suited to provide it.
 
-Track the progress of your feature suggestion by referencing the [Suggestion states and FAQ](./report-a-problem.yml).
+Track the progress of your feature suggestion by referencing the [Suggestion states and FAQ](/visualstudio/ide/how-to-report-a-problem-with-visual-studio).
 
 ## Discussion etiquette
 

docs/ide/find-and-fix-code-errors.md

@@ -157,5 +157,5 @@ To learn more about unit tests in Visual Studio and how they can help you create
 ## Related content
 
 - [First look at the debugger](../debugger/debugger-feature-tour.md)
-- [Generate, fix, and refactor code](../ide/code-generation-in-visual-studio.md)
+- [Generate, fix, and refactor code](/visualstudio/ide/writing-code-in-the-code-and-text-editor#generate-fix-or-refactor-code)
 - [Explore the debugger documentation](../debugger/index.yml)

docs/ide/how-to-add-or-remove-references-by-using-the-reference-manager.md

@@ -107,7 +107,7 @@ Some components in the list might not be shown, depending on the framework versi
 
 For more about version compatibility between .NET Framework versions, see [Version compatibility](/dotnet/framework/migration-guide/version-compatibility).
 
-You should avoid adding file references to outputs of another project in the same solution, because doing so might cause compilation errors. Instead, use the **Projects** tab of the **Add Reference** dialog box to create project-to-project references. This practice makes team development easier by enabling better management of the class libraries you create in your projects. For more information, see [Troubleshoot broken references](../ide/troubleshooting-broken-references.md).
+You should avoid adding file references to outputs of another project in the same solution, because doing so might cause compilation errors. Instead, use the **Projects** tab of the **Add Reference** dialog box to create project-to-project references. This practice makes team development easier by enabling better management of the class libraries you create in your projects. For more information, see [Troubleshoot broken references](/troubleshoot/developer/visualstudio/project-build/troubleshooting-broken-references).
 
 > [!NOTE]
 > A file reference instead of a project reference is created if the target framework version of one project is .NET Framework 4.5 or later, and the target version of the other project is .NET Framework 2, 3, 3.5, or 4.0. For more information about .NET, .NET Framework, and .NET Core, see [What is .NET (and .NET Core)](/dotnet/core/introduction).
@@ -188,7 +188,7 @@ You can use the **Browse** button to browse for a component or assembly in the f
 
 A project can reference a component that targets a different framework version. For example, you could create an application that targets .NET Framework 4.7.2 but references a component that targets .NET Framework 4. For more information, see [Framework targeting overview](../ide/visual-studio-multi-targeting-overview.md).
 
-Avoid adding file references to outputs of another project in the same solution, because this tactic might cause compilation errors. Instead, use the **Solution** tab of the Reference Manager dialog box to create project-to-project references. This makes team development easier by enabling better management of the class libraries that you create in your projects. For more information, see [Troubleshoot broken references](../ide/troubleshooting-broken-references.md).
+Avoid adding file references to outputs of another project in the same solution, because this tactic might cause compilation errors. Instead, use the **Solution** tab of the Reference Manager dialog box to create project-to-project references. This makes team development easier by enabling better management of the class libraries that you create in your projects. For more information, see [Troubleshoot broken references](/troubleshoot/developer/visualstudio/project-build/troubleshooting-broken-references).
 
 You can't browse to an SDK and add it to your project. You can only browse to a file (for example, an assembly or *.winmd*) and add it to your project.
 
@@ -226,5 +226,5 @@ For more information, see [Remove unused references](reference/remove-unused-ref
 ## Related content
 
 - [Manage references in a project](managing-references-in-a-project.md)
-- [Troubleshoot broken references](troubleshooting-broken-references.md)
+- [Troubleshoot broken references](/troubleshoot/developer/visualstudio/project-build/troubleshooting-broken-references)
 - [NuGet versus SDK as a project reference](../extensibility/nuget-versus-sdk-references.md)

docs/ide/how-to-sign-application-and-deployment-manifests.md

@@ -107,7 +107,7 @@ To generate unsigned manifests that include all files in the hash, you must firs
 
 1. On the **Signing** tab, clear the **Sign the ClickOnce manifests** check box.
 
-1. On the **Publish** tab, reset the publish version so that only one version of your application is available. Clear the checkbox for **Automatically increment the version with each publish**. By default, Visual Studio automatically increments the revision number of the publish version every time that you publish an application. For more information, see [How to: Set the ClickOnce publish version](../deployment/how-to-set-the-clickonce-publish-version.md).
+1. On the **Publish** tab, reset the publish version so that only one version of your application is available. Clear the checkbox for **Automatically increment the version with each publish**. By default, Visual Studio automatically increments the revision number of the publish version every time that you publish an application. For more information, see [How to: Set the ClickOnce publish version](/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files).
 
 1. Publish the application. Visual Studio tells you that the application was signed with a different key than the existing application on the server, and asks if you want to overwrite it. Choose **Yes**.
 
@@ -126,5 +126,5 @@ To generate unsigned manifests that include all files in the hash, you must firs
 
 - [Strong-named assemblies](/dotnet/framework/app-domains/strong-named-assemblies)
 - [How to: Create a public-private key pair](/dotnet/framework/app-domains/how-to-create-a-public-private-key-pair)
-- [Signing page, Project Designer](../ide/reference/signing-page-project-designer.md)
+- [Signing page, Project Designer](/visualstudio/ide/how-to-sign-application-and-deployment-manifests)
 - [ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md)

docs/ide/how-to-specify-build-events-visual-basic.md

@@ -163,7 +163,7 @@ The following procedure shows how to set the minimum operating system version in
 
      When you build the project, this command changes the minimum operating system version in the application manifest to 5.1.2600.0.
 
-     The `$(TargetPath)` macro expresses the full path for the executable being created. Therefore, `$(TargetPath).manifest` specifes the application manifest created in the *bin* directory. Publishing copies this manifest to the publishing location that you set earlier.
+     The `$(TargetPath)` macro expresses the full path for the executable being created. Therefore, `$(TargetPath).manifest` specifies the application manifest created in the *bin* directory. Publishing copies this manifest to the publishing location that you set earlier.
 
 8. Publish the project again. Go to the **Publish** page and click **Publish Now**.
 
@@ -178,6 +178,6 @@ The following procedure shows how to set the minimum operating system version in
 ## Related content
 
 - [Compile page, Project Designer (Visual Basic)](../ide/reference/compile-page-project-designer-visual-basic.md)
-- [Publish page, Project Designer](../ide/reference/publish-page-project-designer.md)
+- [Publish page, Project Designer](/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files)
 - [Pre-build event/Post-build event command line dialog box](../ide/reference/pre-build-event-post-build-event-command-line-dialog-box.md)
 - [How to: Specify build events (C#)](../ide/how-to-specify-build-events-csharp.md)