Merge pull request #9785 from MicrosoftDocs/main638350851372116565sync_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/azure/end-to-end-deployment-entity-framework-core-github-actions.md

@@ -1,7 +1,7 @@
 ---
 title: Deploy an ASP.NET Core app and Database to Container Apps using GitHub Actions
 description: Learn how to use Visual Studio to publish a web app to Azure Container Apps using GitHub actions
-ms.date: 09/16/2022
+ms.date: 11/03/2023
 ms.topic: tutorial
 helpviewer_keywords:
   - "deployment, web app"
@@ -224,7 +224,7 @@ The connection string is now stored securely in the GitHub repository secrets an
     git commit -m "Added GitHub Actions workflow"
     git push
     ```
-2. Navigate to the GitHub repository and select the **Actions** tab. A workflow run should have triggered automatically if the push was successful.
+1. Navigate to the GitHub repository and select the **Actions** tab. A workflow run should have triggered automatically if the push was successful.
 1. Select the active workflow to view the log details for each step as they complete. The migration runs last to update the database in Azure.
 
     :::image type="content" source="./media/end-to-end-deployment-entity-framework-core-github-actions/github-actions-workflow.png" lightbox="./media/end-to-end-deployment-entity-framework-core-github-actions/github-actions-workflow-large.png" alt-text="A screenshot showing the GitHub action workflow.":::

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

@@ -1,7 +1,7 @@
 ---
 title: "First look at deployment"
 description: "Learn about your options for deploying apps from Visual Studio."
-ms.date: 03/23/2023
+ms.date: 11/02/2023
 ms.topic: conceptual
 dev_langs:
   - "FSharp"
@@ -33,7 +33,7 @@ See the quickstarts and tutorials for step-by-step deployment instructions. For
 
 Deployment to a local folder is typically used for testing or to begin a staged deployment in which another tool is used for final deployment.
 
-- **ASP.NET**, **ASP.NET Core**, **Node.js**, **Python**, and .**NET Core**: Use the **Publish** tool to deploy to a local folder. The exact options available depend on your app type. In Solution Explorer, right-click your project and select **Publish**. (If you haven't previously configured any publishing profiles, you must then select **Create new profile**.) Next, select **Folder**. For more information, see [Publish an ASP.NET app](quickstart-deploy-aspnet-web-app.md?tabs=folder).
+- **ASP.NET**, **ASP.NET Core**, **Node.js**, **Python**, **.NET Core**, and **.NET 5 and later**: Use the **Publish** tool to deploy to a local folder. The exact options available depend on your app type. In Solution Explorer, right-click your project and select **Publish**. (If you haven't previously configured any publishing profiles, you must then select **Create new profile**.) Next, select **Folder**. For more information, see [Publish an ASP.NET app](quickstart-deploy-aspnet-web-app.md?tabs=folder).
 
     ![Screenshot that shows selecting Publish.](../deployment/media/quickstart-publish.png)
 
@@ -78,11 +78,12 @@ Deployment to a local folder is typically used for testing or to begin a staged
   - [Deploy a .NET Windows desktop app using ClickOnce](quickstart-deploy-using-clickonce-folder.md)
   - [Deploy a C++/CLR app using ClickOnce](/cpp/windows/clickonce-deployment-for-visual-cpp-applications)
 
+:::moniker range="<=vs-2019"
 ## Create an installer package (Windows desktop)
 
 If you require a more complex installation of a desktop application than ClickOnce can provide, you can create a Windows Installer package (MSI or EXE installation file) or a custom bootstrapper.
 
-- An MSI-based installer package can be created by using the [WiX Toolset Visual Studio 2017 Extension](https://marketplace.visualstudio.com/items?itemName=RobMensching.WixToolsetVisualStudio2017Extension). This is a command-line toolset.
+- An MSI-based installer package can be created by using the [WiX Toolset Visual Studio 2019 Extension](https://marketplace.visualstudio.com/items?itemName=WixToolset.WixToolsetVisualStudio2019Extension). This is a command-line toolset.
 
 - An MSI or EXE installer package can be created by using a Setup project (vdproj). To use this option, see [Visual Studio Installer Projects Extension and .NET 6.0](../deployment/installer-projects-net-core.md) or, go directly to the [Visual Studio Installer Projects extension](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.MicrosoftVisualStudio2017InstallerProjects#overview).
 
@@ -92,7 +93,23 @@ If you require a more complex installation of a desktop application than ClickOn
   > InstallShield Limited Edition is no longer included with Visual Studio and isn't supported in Visual Studio 2017 and later versions. Check with Flexera Software about future availability.
 
 - You can also install prerequisite components for desktop applications by configuring a generic installer package, which is known as a bootstrapper. For more information, see [Application deployment prerequisites](../deployment/application-deployment-prerequisites.md).
+:::moniker-end
+:::moniker range=">=vs-2022"
+## Create an installer package (Windows desktop)
+
+If you require a more complex installation of a desktop application than ClickOnce can provide, you can create a Windows Installer package (MSI or EXE installation file) or a custom bootstrapper.
+
+- An MSI-based installer package can be created by using the [WiX Toolset Visual Studio 2022 Extension](https://marketplace.visualstudio.com/items?itemName=WixToolset.WixToolsetVisualStudio2022Extension). This is a command-line toolset.
+
+- An MSI or EXE installer package can be created by using a Setup project (vdproj). To use this option, see [Visual Studio Installer Projects Extension and .NET 6.0](../deployment/installer-projects-net-core.md) or, go directly to the [Visual Studio Installer Projects extension](https://marketplace.visualstudio.com/items?itemName=VisualStudioProductTeam.MicrosoftVisualStudio2017InstallerProjects#overview).
 
+- An MSI or EXE installer package can be created by using [InstallShield](https://www.revenera.com/install/products/installshield/installshield-requirements) from Flexera Software. InstallShield may be used with Visual Studio 2017 and later versions. Community Edition isn't supported.
+
+  > [!NOTE]
+  > InstallShield Limited Edition is no longer included with Visual Studio and isn't supported in Visual Studio 2017 and later versions. Check with Flexera Software about future availability.
+
+- You can also install prerequisite components for desktop applications by configuring a generic installer package, which is known as a bootstrapper. For more information, see [Application deployment prerequisites](../deployment/application-deployment-prerequisites.md).
+:::moniker-end
 ## Publish to Microsoft Store
 
 From Visual Studio, you can create app packages for deployment to Microsoft Store.

docs/ide/walkthrough-building-an-application.md

@@ -1,7 +1,7 @@
 ---
 title: 'Tutorial: Build an application'
 description: Become more familiar with several options that you can configure when you build applications with Visual Studio.
-ms.date: 08/15/2023
+ms.date: 11/02/2023
 ms.technology: vs-ide-compile
 ms.topic: tutorial
 author: ghogen

docs/msbuild/msbuild.md

@@ -1,7 +1,7 @@
 ---
 title: MSBuild
 description: Learn about how the Microsoft Build Engine (MSBuild) platform provides a project file with an XML schema to control builds.
-ms.date: 3/15/2023
+ms.date: 11/03/2023
 ms.topic: conceptual
 helpviewer_keywords:
 - MSBuild, about MSBuild
@@ -173,7 +173,7 @@ The command line `dotnet build --help` lists the command-line options specific t
 
 ## <a name="BKMK_Multitargeting"></a> Multitargeting
 
- By using Visual Studio, you can compile an application to run on any one of several versions of .NET Framework. For example, you can compile an application to run on .NET Framework 2.0 on a 32-bit platform, and you can compile the same application to run on .NET Framework 4.5 on a 64-bit platform. The ability to compile to more than one framework is named multitargeting.
+ By using Visual Studio, you can compile an application to run on any one of several versions of .NET Framework or .NET Core, including .NET 5 and later. For example, you can compile an application to run on .NET Framework 4 on a 32-bit platform, and you can compile the same application to run on .NET Framework 4.8 on a 64-bit platform. The ability to compile to more than one framework is named multitargeting.
 
  These are some of the benefits of multitargeting: