Merge pull request #13963 from Mikejo5000/mikejo-link-fixes

JamesJBarnett · web-flow · commit cdaa15b1b028 · 2025-06-02T15:31:39.000-07:00
Update redirected links in /ide folder
diff --git a/docs/ide/advanced-feature-overview.md b/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
 
diff --git a/docs/ide/build-actions.md b/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. |
diff --git a/docs/ide/create-a-visual-basic-winform-in-visual-studio.md b/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:
 
diff --git a/docs/ide/create-csharp-winform-visual-studio.md b/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:
 
diff --git a/docs/ide/customizing-project-and-item-templates.md b/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)
diff --git a/docs/ide/developer-community-guidelines.md b/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
 
diff --git a/docs/ide/find-and-fix-code-errors.md b/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)
diff --git a/docs/ide/how-to-add-or-remove-references-by-using-the-reference-manager.md b/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)
diff --git a/docs/ide/how-to-sign-application-and-deployment-manifests.md b/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)
diff --git a/docs/ide/how-to-specify-build-events-visual-basic.md b/docs/ide/how-to-specify-build-events-visual-basic.md
@@ -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)
diff --git a/docs/ide/managing-application-resources-dotnet.md b/docs/ide/managing-application-resources-dotnet.md
@@ -109,7 +109,7 @@ Resources are managed differently in .NET projects than in other project types.
 
 ## Support options
 
-If you run into a problem with managing application resources, see [Troubleshoot errors in the Resource Editor](troubleshoot-resource-editor-errors.md).
+If you run into a problem with managing application resources, see [Troubleshoot errors in the Resource Editor](/troubleshoot/developer/visualstudio/project-build/troubleshoot-resource-editor-errors).
 
 ## Related content
 
diff --git a/docs/ide/managing-project-and-solution-properties.md b/docs/ide/managing-project-and-solution-properties.md
@@ -80,7 +80,7 @@ C++ and JavaScript projects have a different user interface for managing project
 
 :::image type="content" source="media/vs-2022/properties-page-cpp-console.png" alt-text="Screenshot of the C++ project properties page.":::
 
-For information about C++ project properties, see [Work with project properties (C++)](/cpp/build/working-with-project-properties). For more information about JavaScript properties, see [Property pages, JavaScript](../ide/reference/property-pages-javascript.md).
+For information about C++ project properties, see [Work with project properties (C++)](/cpp/build/working-with-project-properties). For more information about JavaScript properties, see [Property pages, JavaScript](/previous-versions/visualstudio/visual-studio-2017/ide/reference/property-pages-javascript).
 
 ## Solution properties
 
diff --git a/docs/ide/managing-references-in-a-project.md b/docs/ide/managing-references-in-a-project.md
@@ -128,7 +128,7 @@ For more information, see [Framework targeting overview](../ide/visual-studio-mu
 
 Project-to-project references are references to projects that contain assemblies; you add project references by using the **Projects** tab of the Reference Manager dialog box. Visual Studio can find an assembly when given a path to the project.
 
-When you have a project that produces an assembly, you should reference the project and not use a file reference. The advantage of a project-to-project reference is that it creates a dependency between the projects in the build system. The dependent project is built if it has changed since the last time the referencing project was built. A file reference doesn't create a build dependency, so it's possible to build the referencing project without building the dependent project, and the reference can become obsolete. (That is, the project can reference a previously built version of the project.) This can result in several versions of a single DLL being required in the *bin* directory, which isn't possible. When this conflict occurs, a message appears, such as "Warning: the dependency 'file' in project 'project' can't be copied to the run directory because it would overwrite the reference 'file.'" For more information, see [Troubleshoot broken references](../ide/troubleshooting-broken-references.md) and [How to: Create and remove project dependencies](../ide/how-to-create-and-remove-project-dependencies.md).
+When you have a project that produces an assembly, you should reference the project and not use a file reference. The advantage of a project-to-project reference is that it creates a dependency between the projects in the build system. The dependent project is built if it has changed since the last time the referencing project was built. A file reference doesn't create a build dependency, so it's possible to build the referencing project without building the dependent project, and the reference can become obsolete. (That is, the project can reference a previously built version of the project.) This can result in several versions of a single DLL being required in the *bin* directory, which isn't possible. When this conflict occurs, a message appears, such as "Warning: the dependency 'file' in project 'project' can't be copied to the run directory because it would overwrite the reference 'file.'" For more information, see [Troubleshoot broken references](/troubleshoot/developer/visualstudio/project-build/troubleshooting-broken-references) and [How to: Create and remove project dependencies](../ide/how-to-create-and-remove-project-dependencies.md).
 
 > [!NOTE]
 > A file reference instead of a project-to-project reference is created if the target version of the .NET Framework of one project is version 4.5, and the target version of the other project is version 2, 3, 3.5, or 4.0.
@@ -143,5 +143,5 @@ File references are direct references to assemblies outside the context of a Vis
 
 ## Related content
 
-- [Troubleshoot broken references](../ide/troubleshooting-broken-references.md)
+- [Troubleshoot broken references](/troubleshoot/developer/visualstudio/project-build/troubleshooting-broken-references)
 - [How to: Add or remove references](../ide/how-to-add-or-remove-references-by-using-the-reference-manager.md)
diff --git a/docs/ide/productivity-features.md b/docs/ide/productivity-features.md
@@ -188,7 +188,7 @@ At any one time, you may be working in multiple code files and moving among seve
 
    You can also manage files more easily by creating another instance of **Solution Explorer** and moving it to another monitor. To create another instance of **Solution Explorer**, open a shortcut menu in **Solution Explorer**, and then choose **New Solution Explorer View**.
 
-- **Customize the fonts that appear in Visual Studio**. You can change the font face, size, and color that's used for text in the IDE. For example, you can customize the color of specific code elements in the editor and the font face in tool windows or throughout the IDE. For more information, see [How to: Change fonts and colors](../ide/how-to-change-fonts-and-colors-in-visual-studio.md) and [How to: Change fonts and colors in the editor](../ide/reference/how-to-change-fonts-and-colors-in-the-editor.md).
+- **Customize the fonts that appear in Visual Studio**. You can change the font face, size, and color that's used for text in the IDE. For example, you can customize the color of specific code elements in the editor and the font face in tool windows or throughout the IDE. For more information, see [How to: Change fonts and colors](../ide/how-to-change-fonts-and-colors-in-visual-studio.md) and [How to: Change fonts and colors in the editor](/visualstudio/ide/how-to-change-fonts-and-colors-in-visual-studio).
 
 ## Related content
 
diff --git a/docs/ide/understanding-build-configurations.md b/docs/ide/understanding-build-configurations.md
@@ -45,7 +45,7 @@ To create, select, modify, or delete a configuration, you can use the **Configur
 ![Screenshot of Configuration Manager dialog.](media/understanding-build-configurations/config-manager.png)
 
 > [!NOTE]
-> If you can't find solution configuration settings on the toolbar and can't access the **Configuration Manager**, it might be because you're using Visual Basic development settings. For more information, see [How to: Manage configurations with Visual Basic developer settings applied](../ide/how-to-manage-build-configurations-with-visual-basic-developer-settings-applied.md).
+> If you can't find solution configuration settings on the toolbar and can't access the **Configuration Manager**, it might be because you're using Visual Basic development settings. For more information, see [How to: Manage configurations with Visual Basic developer settings applied](/visualstudio/ide/understanding-build-configurations).
 
 By default, **Debug** and **Release** configurations are included in projects that are created by using Visual Studio templates. A **Debug** configuration supports the debugging of an app, and a **Release** configuration builds a version of the app that can be deployed. For more information, see [How to: Set debug and release configurations](../debugger/how-to-set-debug-and-release-configurations.md). You can also create custom solution configurations and project configurations. For more information, see [How to: Create and edit configurations](../ide/how-to-create-and-edit-configurations.md).
 
diff --git a/docs/ide/visual-studio-multi-targeting-overview.md b/docs/ide/visual-studio-multi-targeting-overview.md
@@ -118,7 +118,7 @@ You must reload the project after making this change. After that, if you open th
 ::: moniker-end
 
 > [!NOTE]
-> If your code contains references to a different version of the .NET than the one that you targeted, error messages may appear when you compile or run the code. To resolve these errors, modify the references. See [Troubleshoot .NET targeting errors](../msbuild/troubleshooting-dotnet-framework-targeting-errors.md).
+> If your code contains references to a different version of the .NET than the one that you targeted, error messages may appear when you compile or run the code. To resolve these errors, modify the references. See [Troubleshoot .NET targeting errors](/troubleshoot/developer/visualstudio/project-build/troubleshooting-dotnet-framework-targeting-errors).
 
 > [!TIP]
 > Depending on the target framework, it can be represented in the following ways in the project file:
diff --git a/docs/ide/writing-code-in-the-code-and-text-editor.md b/docs/ide/writing-code-in-the-code-and-text-editor.md
