Merge pull request #10780 from MicrosoftDocs/main638842250144666824sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/deployment/application-deployment-prerequisites.md

@@ -23,7 +23,7 @@ ms.subservice: deployment
 
 To successfully install and run a Windows desktop application, the components upon which your application depends must be installed onto the target computer. This article provides an overview of the installation of required components for [ClickOnce](../deployment/clickonce-security-and-deployment.md) and Windows Installer [Setup](../deployment/deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop-1) projects.
 
-You can select required components, called prerequisites, such as the .NET Framework and any other redistributable as a part of your installation. The process of installing prerequisites is known as *bootstrapping*. Visual Studio generates a Windows executable program named *Setup.exe*, also known as a *bootstrapper*. The bootstrapper is responsible for installing these prerequisites before your application runs. For more information about selecting these prerequisites, see [Prerequisites dialog box](../ide/reference/prerequisites-dialog-box.md).
+You can select required components, called prerequisites, such as the .NET Framework and any other redistributable as a part of your installation. The process of installing prerequisites is known as *bootstrapping*. Visual Studio generates a Windows executable program named *Setup.exe*, also known as a *bootstrapper*. The bootstrapper is responsible for installing these prerequisites before your application runs. For more information about selecting these prerequisites, see [Prerequisites dialog box](/visualstudio/deployment/how-to-install-prerequisites-with-a-clickonce-application).
 
 A *bootstrapper package* is a group of directories and files containing the manifest files that describe how the prerequisites are installed. Each prerequisite that appears in the **Prerequisites Dialog Box** is a bootstrapper package. If your application prerequisites aren't listed in the **Prerequisite Dialog Box**, you can create custom bootstrapper packages and add them to Visual Studio. Then you can select the prerequisites in the **Prerequisites Dialog Box**. For more information, see [Create bootstrapper packages](../deployment/creating-bootstrapper-packages.md).
 

docs/deployment/code-access-security-for-clickonce-applications.md

@@ -50,9 +50,9 @@ ClickOnce applications are based on the .NET Framework and are subject to code a
 
  Applications deployed from different locations are granted different levels of permissions without prompting. For example, when an application is deployed from the Internet, it receives a highly restrictive set of permissions. When installed from a local Intranet, it receives more permissions, and when installed from a CD-ROM, it receives Full Trust permissions.
 
- As a starting point for configuring permissions, you can select a security zone from the **Zone** list on the **Security** page. If your application will potentially be deployed from more than one zone, select the zone with the least permissions. For more information, see [How to: Set a security zone for a ClickOnce application](../deployment/how-to-set-a-security-zone-for-a-clickonce-application.md).
+ As a starting point for configuring permissions, you can select a security zone from the **Zone** list on the **Security** page. If your application will potentially be deployed from more than one zone, select the zone with the least permissions. For more information, see [How to: Set a security zone for a ClickOnce application](/visualstudio/deployment/how-to-enable-clickonce-security-settings).
 
- The properties that can be set vary by permission set; not all permission sets have configurable properties. For more information about the full list of permissions that your application can request, see <xref:System.Security.Permissions>. For more information about how to set permissions for a custom zone, see [How to: Set custom permissions for a ClickOnce application](../deployment/how-to-set-custom-permissions-for-a-clickonce-application.md).
+ The properties that can be set vary by permission set; not all permission sets have configurable properties. For more information about the full list of permissions that your application can request, see <xref:System.Security.Permissions>. For more information about how to set permissions for a custom zone, see [How to: Set custom permissions for a ClickOnce application](/visualstudio/deployment/how-to-enable-clickonce-security-settings).
 
 ## Debug an application that has restricted permissions
  As a developer, you most likely run your development computer with Full Trust permissions. Therefore, you do not see the same security exceptions when you debug the application that users may see when they run it with restricted permissions.

docs/deployment/creating-bootstrapper-packages.md

@@ -81,7 +81,7 @@ On 64-bit systems, use the following registry key:
 
 Each redistributable component appears in its own subfolder under the packages directory. The product manifest and redistributable files must be put into this subfolder. Localized versions of the component and package manifests must be put in subfolders named according to Culture Name.
 
-After these files are copied into the bootstrapper folder, the bootstrapper package automatically appears in the Visual Studio **Prerequisites** dialog box. If your custom bootstrapper package does not appear, close and then reopen the **Prerequisites** dialog box. For more information, see [Prerequisites dialog box](../ide/reference/prerequisites-dialog-box.md).
+After these files are copied into the bootstrapper folder, the bootstrapper package automatically appears in the Visual Studio **Prerequisites** dialog box. If your custom bootstrapper package does not appear, close and then reopen the **Prerequisites** dialog box. For more information, see [Prerequisites dialog box](/visualstudio/deployment/how-to-install-prerequisites-with-a-clickonce-application).
 
 The following table shows the properties that are automatically populated by the bootstrapper.
 
@@ -110,6 +110,6 @@ The redistributable list is an XML file that you should name using the following
 
 ## Related content
 - [How to: Install prerequisites with a ClickOnce application](../deployment/how-to-install-prerequisites-with-a-clickonce-application.md)
-- [Prerequisites dialog box](../ide/reference/prerequisites-dialog-box.md)
+- [Prerequisites dialog box](/visualstudio/deployment/how-to-install-prerequisites-with-a-clickonce-application)
 - [Product and package schema reference](../deployment/product-and-package-schema-reference.md)
 - [Use the Visual Studio 2005 bootstrapper to kick-start your installation](/archive/msdn-magazine/2004/october/visual-studio-2005-bootstrapper-start-kick-your-installation)

docs/deployment/deploying-applications-services-and-components.md

@@ -49,7 +49,7 @@ Deployment to a local folder is typically used for testing or to begin a staged
 
   - For continuous (or automated) deployment of apps, use Azure DevOps with [Azure Pipelines](/azure/devops/pipelines/tasks/build/visual-studio-build).
   - For one-time (or manual) deployment of apps, use the [Publish](publish-overview.md) tool in Visual Studio. See [Deploy an ASP.NET Web app](/azure/app-service/quickstart-dotnetcore).
-  - To create GitHub Actions workflows for ASP.NET and Azure Function projects hosted on GitHub.com, see [Deploy to Azure using GitHub Actions](../deployment/azure-deployment-using-github-actions.md).
+  - To create GitHub Actions workflows for ASP.NET and Azure Function projects hosted on GitHub.com, see [Deploy to Azure using GitHub Actions](/visualstudio/azure/azure-deployment-using-github-actions).
   - For deployment using Git, see [Continuous deployment of ASP.NET Core to Azure with Git](/azure/app-service/deploy-continuous-deployment).
 
   To use the **Publish** tool, right-click the project in Solution Explorer and select **Publish**. (If you've previously configured any publishing profiles, you must then select **Create new profile**.) In the **Publish** dialog box, choose **Azure**, and then choose the desired Azure service to continue.

docs/deployment/how-to-publish-a-wpf-application-with-visual-styles-enabled.md

@@ -10,7 +10,7 @@ ms.subservice: deployment
 ---
 # Publish a WPF application with visual styles enabled
 
-Visual styles enable the appearance of common controls to change based on the theme chosen by the user. By default, visual styles are not enabled for Windows Presentation Foundation (WPF) applications, so you must enable them manually. However, enabling visual styles for a WPF application and then publishing the solution causes an error. This topic describes how to resolve this error and the process for publishing a WPF application with visual styles enabled. For more information about visual styles, see [Visual styles overview](/windows/desktop/Controls/visual-styles-overview). For more information about the error message, see [Troubleshoot specific errors in ClickOnce deployments](../deployment/troubleshooting-specific-errors-in-clickonce-deployments.md).
+Visual styles enable the appearance of common controls to change based on the theme chosen by the user. By default, visual styles are not enabled for Windows Presentation Foundation (WPF) applications, so you must enable them manually. However, enabling visual styles for a WPF application and then publishing the solution causes an error. This topic describes how to resolve this error and the process for publishing a WPF application with visual styles enabled. For more information about visual styles, see [Visual styles overview](/windows/desktop/Controls/visual-styles-overview). For more information about the error message, see [Troubleshoot specific errors in ClickOnce deployments](/troubleshoot/developer/visualstudio/ide/troubleshoot-clickonce-deployments).
 
  To resolve the error and to publish the solution, you must perform the following tasks:
 
@@ -170,7 +170,7 @@ Visual styles enable the appearance of common controls to change based on the th
 
 ## Related content
 
-- [Troubleshooting Specific Errors in ClickOnce Deployments](../deployment/troubleshooting-specific-errors-in-clickonce-deployments.md)
+- [Troubleshooting Specific Errors in ClickOnce Deployments](/troubleshoot/developer/visualstudio/ide/troubleshoot-clickonce-deployments)
 - [Visual Styles Overview](/windows/desktop/Controls/visual-styles-overview)
 - [Enabling Visual Styles](/windows/desktop/Controls/cookbook-overview)
 - [Developer Command Prompt and Developer PowerShell](../ide/reference/command-prompt-powershell.md)

docs/deployment/installer-projects-net-core.md

@@ -83,5 +83,5 @@ The **.NET Core Runtime...** option should be selected for console applications,
 
 ## Related content
 
-- [Prerequisites Dialog Box](../ide/reference/prerequisites-dialog-box.md)
+- [Prerequisites Dialog Box](/visualstudio/deployment/how-to-install-prerequisites-with-a-clickonce-application)
 - [Application Deployment Prerequisites](../deployment/application-deployment-prerequisites.md)

docs/deployment/publishing-clickonce-applications.md

@@ -53,7 +53,7 @@ When publishing a ClickOnce application for the first time, publish properties c
 |[Set the ClickOnce publish version](../deployment/how-to-specify-where-visual-studio-copies-the-files.md#set-the-clickonce-publish-version)|Describes how to set the ClickOnce **Publish Version** property, which determines whether or not the application that you are publishing will be treated as an update.|
 |[Automatically increment the ClickOnce publish version](../deployment/how-to-specify-where-visual-studio-copies-the-files.md#automatically-increment-the-clickonce-publish-version)|Describes how to automatically increment the Revision number of the **PublishVersion** each time you publish the application.|
 
- For more information, see [Publish Page, Project Designer](../ide/reference/publish-page-project-designer.md)
+ For more information, see [Publish Page, Project Designer](/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files)
 
 ### Application Files dialog box
  This dialog box allows you to specify how the files in your project are categorized for publishing, dynamic downloading, and updating. It contains a grid that lists the project files that are not excluded by default, or that have a download group.

docs/deployment/securing-clickonce-applications.md

@@ -48,7 +48,7 @@ ClickOnce applications are subject to code access security constraints in the .N
  For more information about code access security and ClickOnce, see [Code access security for ClickOnce applications](../deployment/code-access-security-for-clickonce-applications.md).
 
 ## Code-signing certificates
- To publish an application by using ClickOnce deployment, you can sign the application and deployment manifests for the application by using a public/private key pair. The tools for signing a manifest are available on the **Signing** page of the **Project Designer**. For more information, see [Signing Page, Project Designer](../ide/reference/signing-page-project-designer.md).
+ To publish an application by using ClickOnce deployment, you can sign the application and deployment manifests for the application by using a public/private key pair. The tools for signing a manifest are available on the **Signing** page of the **Project Designer**. For more information, see [Signing Page, Project Designer](/visualstudio/ide/how-to-sign-application-and-deployment-manifests).
 
  After the manifests are signed, the publisher information based on the Authenticode signature will be displayed to the user in the permissions dialog box during installation, to show the user that the application originated from a trusted source.
 

docs/deployment/troubleshooting-clickonce-deployments.md

@@ -42,7 +42,7 @@ This topic helps you diagnose and resolve the most common issues with ClickOnce
 
  Describes miscellaneous issues surrounding ClickOnce deployments.
 
- [Troubleshoot specific errors in ClickOnce deployments](../deployment/troubleshooting-specific-errors-in-clickonce-deployments.md)
+ [Troubleshoot specific errors in ClickOnce deployments](/troubleshoot/developer/visualstudio/ide/troubleshoot-clickonce-deployments)
 
  Describes specific scenarios in which a ClickOnce deployment cannot succeed, and provides steps for resolving them.