Merge pull request #10621 from MicrosoftDocs/main638749115324605146sync_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

@@ -1,7 +1,7 @@
 ---
 title: "Application Deployment Prerequisites"
 description: Learn about the deployment prerequisites for your applications, including using the Prerequisites Dialog Box and bootstrapper packages.
-ms.date: "09/23/2021"
+ms.date: "02/10/2025"
 ms.topic: "conceptual"
 dev_langs:
   - "FSharp"
@@ -21,16 +21,16 @@ ms.subservice: deployment
 ---
 # Application deployment prerequisites (Windows desktop)
 
-To have your Windows desktop application install and run successfully, first install all components upon which your application is dependent onto the target computer. For example, most applications created using Visual Studio have a dependency on the .NET Framework. In this case, the correct version of the common language runtime must be present on the destination computer before the application is installed.
+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 these prerequisites in the **Prerequisites Dialog Box** and install the .NET Framework and any other redistributable as a part of your installation. This practice 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](../ide/reference/prerequisites-dialog-box.md).
 
-Each prerequisite is a bootstrapper package. A bootstrapper package is a group of directories and files containing the manifest files that describe how the prerequisites are installed. If your application prerequisites are not 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).
+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).
 
-By default, bootstrapping is enabled for both Windows Installer deployment (by using Setup projects in Visual Studio) and ClickOnce deployment. The bootstrapper generated for Windows Installer deployment is not signed, but in ClickOnce deployment, the bootstrapper is signed. You can disable bootstrapping for a component, but you should do so only if you are sure that the correct version of the component is already installed on all target computers.
+By default, bootstrapping is enabled for both Windows Installer deployment (by using Setup projects in Visual Studio) and ClickOnce deployment. The bootstrapper generated for Windows Installer deployment isn't signed, but in ClickOnce deployment, the bootstrapper is signed. You can disable bootstrapping for a component, but you should do so only if you're sure that the correct version of the component is already installed on all target computers.
 
 ## Bootstrapping and ClickOnce deployment
- Before installing an application on a client computer, ClickOnce examines the client to ensure that it has the requirements specified in the application manifest. These include the following requirements:
+ Before installing an application on a client computer, ClickOnce examines the client to ensure that it has the requirements specified in the application manifest. These requirements include the following:
 
 - The minimum required version of the common language runtime, which is specified as an assembly dependency in the application manifest.
 
@@ -45,17 +45,12 @@ By default, bootstrapping is enabled for both Windows Installer deployment (by u
 
  If you use Visual Studio and ClickOnce to deploy your application, the bootstrapper packages that are selected by default depend on the version of the .NET Framework in the solution. However, if you change the target .NET Framework version, you must update the options in the **Prerequisites Dialog Box** manually.
 
-|Target .NET Framework|Selected Bootstrapper Packages|
-|---------------------------|------------------------------------|
-|.NET Framework 4 Client Profile|.NET Framework 4 Client Profile<br /><br /> Windows Installer 3.1|
-|.NET Framework 4|.NET Framework 4<br /><br /> Windows Installer 3.1|
-
  With ClickOnce deployment, the *Publish.htm* page generated by the ClickOnce Publish Wizard points either to a link that installs only the application, or to a link that installs both the application and the bootstrapped components.
 
  If you generate the bootstrapper by using the ClickOnce Publish Wizard or the Publish Page in Visual Studio, the *Setup.exe* is automatically signed. However, if you want to use your customer's certificate to sign the bootstrapper, you can sign the file later.
 
 ## Bootstrapping and MSBuild
- If you do not use Visual Studio, but rather compile your applications on the command line, you can create the ClickOnce bootstrapping application by using a Microsoft Build Engine (MSBuild) task. For more information, see [GenerateBootstrapper task](../msbuild/generatebootstrapper-task.md).
+ If you don't use Visual Studio, but rather compile your applications on the command line, you can create the ClickOnce bootstrapping application by using a Microsoft Build Engine (MSBuild) task. For more information, see [GenerateBootstrapper task](../msbuild/generatebootstrapper-task.md).
 
  As an alternative to bootstrapping, you can pre-deploy components using an electronic software distribution system, such as Microsoft Systems Management Server (SMS).
 
@@ -73,7 +68,7 @@ By default, bootstrapping is enabled for both Windows Installer deployment (by u
 | **-homesite=** `true` **&#124;** `false` | When `true`, downloads the dependencies from the preferred location on the vendor's site. This setting overrides the **-componentsurl** setting. When `false`, downloads the dependencies from the URL specified by **-componentsurl**. |
 
 ## Operating system support
- The Visual Studio bootstrapper is not supported on Windows Server 2008 Server Core or Windows Server 2008 R2 Server Core, as they provide a low-maintenance server environment with limited functionality. For example, the Server Core installation option only supports the .NET Framework 3.5 Server Core profile, which cannot run the Visual Studio features that depend on the full .NET Framework.
+ The Visual Studio bootstrapper isn't supported on Windows Server 2008 Server Core or Windows Server 2008 R2 Server Core, as they provide a low-maintenance server environment with limited functionality. For example, the Server Core installation option only supports the .NET Framework 3.5 Server Core profile, which can't run the Visual Studio features that depend on the full .NET Framework.
 
 ## Related content
 - [Choose a ClickOnce deployment strategy](../deployment/choosing-a-clickonce-deployment-strategy.md)

docs/deployment/index.yml

@@ -60,7 +60,7 @@ landingContent:
           - text: ClickOnce
             url: quickstart-deploy-using-clickonce-folder.md
           - text: Installer package
-            url: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop
+            url: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop-1
       - linkListType: how-to-guide
         links:
           - text: Package a desktop app for Windows Store
@@ -74,7 +74,7 @@ landingContent:
           - text: ClickOnce
             url: how-to-publish-a-clickonce-application-using-the-publish-wizard.md
           - text: Installer package
-            url: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop
+            url: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop-1
 
   # Card
   - title: Deploy to Azure

docs/deployment/toc.yml

@@ -226,7 +226,7 @@
       - name: Visual Studio Installer Projects Extension and .NET 6.0
         href: installer-projects-net-core.md
       - name: Create an installer package (Windows desktop)
-        href: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop
+        href: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop-1
     - name: Custom bootstrapper
       items:
       - name: Application deployment prerequisites