Merged main into live

mijacobs · mijacobs · commit e829bff26fe7 · 2025-06-24T01:02:29.000Z
diff --git a/docs/azure/overview-github-actions.md b/docs/azure/overview-github-actions.md
@@ -37,7 +37,7 @@ If your codebase is hosted on GitHub.com and your deployment target is an Azure
 
 Visual Studio also simplifies the process by handling your application secrets for you.
 
-Get started by right-clicking on your project in Solution Explorer and selecting **Publish** from the context menu. For a tutorial, see [Deploy your application to Azure using GitHub Actions workflows created by Visual Studio](../deployment/azure-deployment-using-github-actions.md).
+Get started by right-clicking on your project in Solution Explorer and selecting **Publish** from the context menu. For a tutorial, see [Deploy your application to Azure using GitHub Actions workflows created by Visual Studio](/visualstudio/azure/azure-deployment-using-github-actions).
 
 ## How do I get my project on GitHub.com?
 
diff --git a/docs/azure/vs-azure-tools-debug-cloud-services-virtual-machines.md b/docs/azure/vs-azure-tools-debug-cloud-services-virtual-machines.md
@@ -240,7 +240,7 @@ You can debug programs that run in Azure App Service by using the Attach to Proc
 You can debug programs that run on Azure Virtual Machines by using Server Explorer in Visual Studio. When you enable remote debugging on an Azure virtual machine, Azure installs the remote debugging extension on the virtual machine. Then, you can attach to processes on the virtual machine and debug as you normally would.
 
 > [!NOTE]
-> Virtual Machines created through the Azure Resource Manager stack can be remotely debugged by using Cloud Explorer in Visual Studio 2019. For more information, see [Managing Azure Resources with Cloud Explorer](vs-azure-tools-resources-managing-with-cloud-explorer.md).
+> Virtual Machines created through the Azure Resource Manager stack can be remotely debugged by using Cloud Explorer in Visual Studio 2019. For more information, see [Managing Azure Resources with Cloud Explorer](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-resources-managing-with-cloud-explorer).
 
 ### To debug an Azure virtual machine
 
diff --git a/docs/azure/vs-azure-tools-diagnostics-for-cloud-services-and-virtual-machines.md b/docs/azure/vs-azure-tools-diagnostics-for-cloud-services-and-virtual-machines.md
@@ -190,7 +190,7 @@ After you've collected the diagnostics data for a cloud service or virtual machi
    | Custom log files |Logs of data that you predefined. |You can specify in code the location of custom log files in your storage account. For example, you can specify a custom blob container. |
 4. If data of any type is truncated, you can try increasing the buffer for that data type or shortening the interval between transfers of data from the virtual machine to your storage account.
 5. (Optional) Purge data from the storage account occasionally to reduce overall storage costs.
-6. When you do a full deployment, the *diagnostics.cscfg* file is updated in Azure, and your cloud service picks up any changes to your diagnostics configuration. If you instead update an existing deployment, the .cscfg file isn't updated in Azure. You can still change diagnostics settings, though, by following the steps in the next section. For more information about performing a full deployment and updating an existing deployment, see [Publish Azure Application Wizard](vs-azure-tools-publish-azure-application-wizard.md).
+6. When you do a full deployment, the *diagnostics.cscfg* file is updated in Azure, and your cloud service picks up any changes to your diagnostics configuration. If you instead update an existing deployment, the .cscfg file isn't updated in Azure. You can still change diagnostics settings, though, by following the steps in the next section. For more information about performing a full deployment and updating an existing deployment, see [Publish Azure Application Wizard](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-publish-azure-application-wizard).
 
 ### To view virtual machine diagnostics data
 
diff --git a/docs/azure/vs-azure-tools-emulator-express-debug-run.md b/docs/azure/vs-azure-tools-emulator-express-debug-run.md
@@ -42,8 +42,8 @@ The following issues are known limitations of Emulator Express:
 - Emulator Express is not compatible with IIS Web Server.
 - Your cloud service can contain multiple roles, but each role is limited to one instance.
 - You can't access port numbers below 1000. If you use an authentication provider that normally uses a port below 1000, you might need to change this value to a port number that's above 1000.
-- Any limitations that apply to the Azure Compute Emulator also apply to Emulator Express. For example, you can't have more than 50 role instances per deployment. For more information about the Azure Compute Emulator, see [Run an Azure Application in the Compute Emulator](vs-azure-tools-performance-profiling-cloud-services.md).
+- Any limitations that apply to the Azure Compute Emulator also apply to Emulator Express. For example, you can't have more than 50 role instances per deployment. For more information about the Azure Compute Emulator, see [Run an Azure Application in the Compute Emulator](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-performance-profiling-cloud-services).
 
 ## Related content
 
-[Debugging Azure Cloud Services (extended support)](vs-azure-tools-debugging-cloud-services-overview.md)
+[Debugging Azure Cloud Services (extended support)](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-debugging-cloud-services-overview)
diff --git a/docs/azure/vs-azure-tools-publishing-a-cloud-service.md b/docs/azure/vs-azure-tools-publishing-a-cloud-service.md
@@ -36,7 +36,7 @@ When you publish your Azure application, you can do one of the following tasks:
 
 - Create a service package: You can use this package and the service configuration file to publish your application to a deployment environment from the [Azure portal](https://portal.azure.com).
 
-- Publish your Azure project from Visual Studio: To publish your application directly to Azure, you use the Publish Wizard. For information, see [Publish Azure Application Wizard](vs-azure-tools-publish-azure-application-wizard.md).
+- Publish your Azure project from Visual Studio: To publish your application directly to Azure, you use the Publish Wizard. For information, see [Publish Azure Application Wizard](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-publish-azure-application-wizard).
 
 ### To create a service package from Visual Studio
 
@@ -159,4 +159,4 @@ You might need to include specific files in your service package so that they ar
 
 ## Related content
 
-To learn more about publishing to Azure from Visual Studio, see [Publish Azure Application Wizard](vs-azure-tools-publish-azure-application-wizard.md).
+To learn more about publishing to Azure from Visual Studio, see [Publish Azure Application Wizard](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-publish-azure-application-wizard).
diff --git a/docs/azure/vs-azure-tools-service-configurations-and-profiles-how-to-manage.md b/docs/azure/vs-azure-tools-service-configurations-and-profiles-how-to-manage.md
@@ -85,7 +85,7 @@ When you run the wizard for the first time, a default profile is created. Visual
 
     The new profile appears in the Target profile list.
 6. In the **Target profile** list, select the profile that you just created. The Publish Wizard settings are filled in with the choices from the profile you selected.
-7. Select the **Previous** and **Next** buttons to display each page of the Publish Wizard, and then customize the settings for this profile. See [Publish Azure Application Wizard](vs-azure-tools-publish-azure-application-wizard.md) for information.
+7. Select the **Previous** and **Next** buttons to display each page of the Publish Wizard, and then customize the settings for this profile. See [Publish Azure Application Wizard](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-publish-azure-application-wizard) for information.
 8. After you finish customizing the settings, select **Next** to go back to the Settings page. The profile is saved when you publish the service by using these settings or if you select **Save** next to the list of profiles.
 
 ### To rename or delete a profile
@@ -100,10 +100,10 @@ When you run the wizard for the first time, a default profile is created. Visual
 
 1. Open the shortcut menu for your Azure project, and then select **Publish**.
 2. In the **Target profile** list, select the profile that you want to change.
-3. Select the **Previous** and **Next** buttons to display each page of the Publish Wizard, and then change the settings you want. See [Publish Azure Application Wizard](vs-azure-tools-publish-azure-application-wizard.md) for information.
+3. Select the **Previous** and **Next** buttons to display each page of the Publish Wizard, and then change the settings you want. See [Publish Azure Application Wizard](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-publish-azure-application-wizard) for information.
 4. After you finish changing the settings, select **Next** to go back to the **Settings** page.
 5. (Optional) select **Publish** to publish the cloud service using the new settings. If you don't want to publish your cloud service at this time, and you close the Publish Wizard, Visual Studio asks you if you want to save the changes to the profile.
 
 ## Related content
 
-To learn about configuring other parts of your Azure project from Visual Studio, see [Configuring an Azure Project](vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address.md).
+To learn about configuring other parts of your Azure project from Visual Studio, see [Configuring an Azure Project](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address).
diff --git a/docs/azure/vs-azure-tools-storage-resources-server-explorer-browse-manage.md b/docs/azure/vs-azure-tools-storage-resources-server-explorer-browse-manage.md
@@ -20,7 +20,7 @@ If you've installed Azure workload for Microsoft Visual Studio 2019, you can vie
 
 To view Server Explorer in Visual Studio, on the menu bar, select **View** > **Server Explorer**. The **Storage** node shows all of the storage accounts that exist under each Azure subscription or certificate that you're connected to. If your storage account doesn't appear, you can add it by following the instructions [later in this article](#add-storage-accounts-by-using-server-explorer).
 
-In Visual Studio 2019 and earlier, you can also use Cloud Explorer to view and manage your Azure resources. For more information, see [Managing Azure resources with Cloud Explorer](vs-azure-tools-resources-managing-with-cloud-explorer.md).
+In Visual Studio 2019 and earlier, you can also use Cloud Explorer to view and manage your Azure resources. For more information, see [Managing Azure resources with Cloud Explorer](/previous-versions/visualstudio/visual-studio-2017/azure/vs-azure-tools-resources-managing-with-cloud-explorer).
 
 > [!IMPORTANT]
 > Cloud Explorer has been retired in Visual Studio 2022. Instead, you can use the following alternatives:
diff --git a/docs/containers/container-tools-react.md b/docs/containers/container-tools-react.md
@@ -436,5 +436,5 @@ You can now pull the container from the registry to any host capable of running
 ## Additional resources
 
 - [Container development with Visual Studio](./index.yml)
-- [Troubleshoot Visual Studio development with Docker](troubleshooting-docker-errors.md)
+- [Troubleshoot Visual Studio development with Docker](/troubleshoot/developer/visualstudio/ide/troubleshooting-docker-errors)
 - [Visual Studio Container Tools GitHub repository](https://github.com/Microsoft/DockerTools)
diff --git a/docs/containers/container-tools.md b/docs/containers/container-tools.md
@@ -166,5 +166,5 @@ You can now pull the container from the registry to any host capable of running
 
 - [Container development with Visual Studio](./index.yml)
 - [Create a multi-container app with Docker Compose](tutorial-multicontainer.md)
-- [Troubleshoot Visual Studio development with Docker](troubleshooting-docker-errors.md)
+- [Troubleshoot Visual Studio development with Docker](/troubleshoot/developer/visualstudio/ide/troubleshooting-docker-errors)
 - [Visual Studio Container Tools GitHub repository](https://github.com/Microsoft/DockerTools)
diff --git a/docs/containers/edit-and-refresh.md b/docs/containers/edit-and-refresh.md
@@ -190,7 +190,7 @@ You can configure when Fast Mode is used; see [How to configure Visual Studio Co
 
 ## Troubleshoot
 
-Learn how to [troubleshoot Visual Studio Docker development](troubleshooting-docker-errors.md).
+Learn how to [troubleshoot Visual Studio Docker development](/troubleshoot/developer/visualstudio/ide/troubleshooting-docker-errors).
 
 ## Related content
 
diff --git a/docs/data-tools/configure-service-reference-dialog-box.md b/docs/data-tools/configure-service-reference-dialog-box.md
@@ -51,7 +51,7 @@ Updates the web address where a service reference looks for a service. For examp
 Determines the code access level for WCF client classes.
 
 > [!NOTE]
-> For Website projects, this option is always set to `Public` and cannot be changed. For more information, see [Troubleshooting service references](../data-tools/troubleshooting-service-references.md).
+> For Website projects, this option is always set to `Public` and cannot be changed. For more information, see [Troubleshooting service references](/troubleshoot/developer/visualstudio/tools-utilities/troubleshooting-service-references).
 
 **Generate asynchronous operations**
 
diff --git a/docs/data-tools/n-tier-data-applications-overview.md b/docs/data-tools/n-tier-data-applications-overview.md
@@ -78,7 +78,7 @@ The data tier cannot be accessed directly from the client in the presentation ti
 
 The following topics provide information about working with n-tier applications:
 
-[Separate datasets and TableAdapters into different projects](../data-tools/separate-datasets-and-tableadapters-into-different-projects.md)
+[Separate datasets and TableAdapters into different projects](/previous-versions/visualstudio/visual-studio-2017/data-tools/separate-datasets-and-tableadapters-into-different-projects?view=vs-2017)
 
 [Walkthrough: Creating an n-tier data application](../data-tools/walkthrough-creating-an-n-tier-data-application.md)
 
diff --git a/docs/data-tools/windows-communication-foundation-services-and-wcf-data-services-in-visual-studio.md b/docs/data-tools/windows-communication-foundation-services-and-wcf-data-services-in-visual-studio.md
@@ -273,10 +273,10 @@ To avoid this problem, types in referenced assemblies are shared by default. If
 | Title | Description |
 | - | - |
 | [Walkthrough: Creating a simple WCF Service in Windows Forms](../data-tools/walkthrough-creating-a-simple-wcf-service-in-windows-forms.md) | Provides a step-by-step demonstration of creating and using WCF services in Visual Studio. |
-| [Walkthrough: Creating a WCF data service with WPF and Entity Framework](../data-tools/walkthrough-creating-a-wcf-data-service-with-wpf-and-entity-framework.md) | Provides a step-by-step demonstration of how to create and use WCF Data Services in Visual Studio. |
+| [Walkthrough: Creating a WCF data service with WPF and Entity Framework](/previous-versions/visualstudio/visual-studio-2017/data-tools/walkthrough-creating-a-wcf-data-service-with-wpf-and-entity-framework) | Provides a step-by-step demonstration of how to create and use WCF Data Services in Visual Studio. |
 | [Using the WCF development tools](/dotnet/framework/wcf/using-the-wcf-development-tools) | Discusses how to create and test WCF services in Visual Studio. |
 | | [How to: Add, update, or remove a WCF Data Service reference](../data-tools/how-to-add-update-or-remove-a-wcf-data-service-reference.md) |
-| [Troubleshooting service references](../data-tools/troubleshooting-service-references.md) | Presents some common errors that can occur with service references and how to prevent them. |
+| [Troubleshooting service references](/troubleshoot/developer/visualstudio/tools-utilities/troubleshooting-service-references) | Presents some common errors that can occur with service references and how to prevent them. |
 | [Debugging WCF services](../debugger/debugging-wcf-services.md) | Describes common debugging problems and techniques you might encounter when debugging WCF services. |
 | [Walkthrough: Creating an n-tier data application](../data-tools/walkthrough-creating-an-n-tier-data-application.md) | Provides step-by-step instructions for creating a typed dataset and separating the TableAdapter and dataset code into multiple projects. |
 | [Configure Service Reference dialog box](../data-tools/configure-service-reference-dialog-box.md) | Describes the user interface elements of the **Configure Service Reference** dialog box. |
diff --git a/docs/data-tools/work-with-datasets-in-n-tier-applications.md b/docs/data-tools/work-with-datasets-in-n-tier-applications.md
@@ -39,10 +39,10 @@ N-tier support in typed datasets enables iterative development of the applicatio
 
 - [N-Tier data applications overview](../data-tools/n-tier-data-applications-overview.md)
 - [Walkthrough: Creating an n-tier Data Application](../data-tools/walkthrough-creating-an-n-tier-data-application.md)
-- [Add code to TableAdapters in n-tier applications](../data-tools/add-code-to-tableadapters-in-n-tier-applications.md)
-- [Add code to datasets in n-tier applications](../data-tools/add-code-to-datasets-in-n-tier-applications.md)
-- [Add validation to an n-tier dataset](../data-tools/add-validation-to-an-n-tier-dataset.md)
-- [Separate datasets and TableAdapters into different projects](../data-tools/separate-datasets-and-tableadapters-into-different-projects.md)
+- [Add code to TableAdapters in n-tier applications](/previous-versions/visualstudio/visual-studio-2017/data-tools/add-code-to-tableadapters-in-n-tier-applications?view=vs-2017)
+- [Add code to datasets in n-tier applications](/previous-versions/visualstudio/visual-studio-2017/data-tools/add-code-to-datasets-in-n-tier-applications?view=vs-2017)
+- [Add validation to an n-tier dataset](/previous-versions/visualstudio/visual-studio-2017/data-tools/add-validation-to-an-n-tier-dataset?view=vs-2017)
+- [Separate datasets and TableAdapters into different projects](/previous-versions/visualstudio/visual-studio-2017/data-tools/separate-datasets-and-tableadapters-into-different-projects?view=vs-2017)
 - [Hierarchical update](../data-tools/hierarchical-update.md)
 - [Dataset tools in Visual Studio](../data-tools/dataset-tools-in-visual-studio.md)
 - [Accessing data in Visual Studio](../data-tools/accessing-data-in-visual-studio.md)
