Merged main into live

Author: mijacobs

.openpublishing.redirection.json

@@ -1590,6 +1590,26 @@
       "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/data-tools/walkthrough-creating-a-wcf-data-service-with-wpf-and-entity-framework",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/ide/reference/signing-page-project-designer.md",
+      "redirect_url": "/visualstudio/ide/how-to-sign-application-and-deployment-manifests",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/advanced-security-settings-dialog-box.md",
+      "redirect_url": "/visualstudio/deployment/how-to-enable-clickonce-security-settings",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/publish-page-project-designer.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/prerequisites-dialog-box.md",
+      "redirect_url": "/visualstudio/deployment/how-to-install-prerequisites-with-a-clickonce-application",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/deployment/how-to-enable-autostart-for-cd-installations.md",
       "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",

docs/deployment/clickonce-security-and-deployment.md

@@ -96,7 +96,7 @@ ClickOnce is a deployment technology that enables you to create self-updating Wi
 |Tool|Description|
 |----------|-----------------|
 |[Security Page, Project Designer](../ide/reference/security-page-project-designer.md)|Signs the application and deployment manifests. For .NET Core and .NET 5+, these settings are in the Publish profile.|
-|[Publish Page, Project Designer](../ide/reference/publish-page-project-designer.md)|Generates and edits the application and deployment manifests for Visual Basic and Visual C# applications. For .NET Core and .NET 5+, these settings are in the Publish profile.|
+|[Specify ClickOnce Publish properties](../deployment/how-to-specify-where-visual-studio-copies-the-files.md)|Generates and edits the application and deployment manifests for Visual Basic and Visual C# applications. For .NET Core and .NET 5+, these settings are in the Publish profile.|
 |[*Mage.exe* (Manifest Generation and Editing Tool)](/dotnet/framework/tools/mage-exe-manifest-generation-and-editing-tool)|Generates the application and deployment manifests for Visual Basic, Visual C#, and Visual C++ applications.<br /><br /> Signs and re-signs the application and deployment manifests.<br /><br /> Can be run from batch scripts and the command prompt.|
 |[*dotnetmage.exe* (Manifest Generation and Editing Tool)](https://github.com/dotnet/deployment-tools/blob/main/docs/dotnet-mage/README.md)|Generates the application and deployment manifests for .NET 5+ C# and Visual Basic applications. The usage is equivalent to *Mage.exe*.<br /><br /> Signs and re-signs the application and deployment manifests.<br /><br /> Can be run from batch scripts and the command prompt.|
 |[*MageUI.exe* (Manifest Generation and Editing Tool, Graphical Client)](/dotnet/framework/tools/mageui-exe-manifest-generation-and-editing-tool-graphical-client)|Generates and edits the application and deployment manifests.<br /><br /> Signs and re-signs the application and deployment manifests.|

docs/deployment/how-to-enable-clickonce-security-settings.md

@@ -3,6 +3,10 @@ title: Enable & configure ClickOnce security
 description: Learn how the Publish wizard automatically enables code access security for ClickOnce applications to publish the application.
 ms.date: 04/25/2025
 ms.topic: how-to
+f1_keywords:
+- vb.ProjectPropertiesSecurity
+- vb.XBAPProjectPropertiesSecurity
+- vs.err.debug_in_zone_no_hostproc
 dev_langs: 
   - VB
   - CSharp
@@ -24,7 +28,7 @@ You can enable and configure ClickOnce security settings in the **Security** pag
 
 ## Enable ClickOnce security settings
 
-Code access security for ClickOnce applications must be enabled in order to publish the application. This is done automatically when you publish an application using the Publish wizard.
+Code access security for ClickOnce applications must be enabled in order to publish the application. This is done automatically when you publish an application using the Publish wizard. For more information about code access security and security zones, see [Code Access Security for ClickOnce Applications](../deployment/code-access-security-for-clickonce-applications.md).
 
 In some cases, enabling code access security can impact performance when building or debugging your application; in these cases, you may wish to temporarily disable the security settings.
 
@@ -101,6 +105,28 @@ You can deploy a ClickOnce application that uses default permissions for the Int
     > [!NOTE]
     > You can use the `ToXml` method of a permission set to generate the XML code for the application manifest. For example, to generate the XML for the <xref:System.Security.Permissions.EnvironmentPermission> permission set, call the <xref:System.Security.Permissions.EnvironmentPermission.ToXml%2A> method.
 
+## Configure debugging for a security zone
+
+You can specify security settings related to debugging in a zone.
+
+1. With a project selected in **Solution Explorer**, on the **Project** menu, click **Properties**.
+
+2. Click the **Security** tab.
+
+3. Select the **Enable ClickOnce Security Settings** check box.
+
+4. Select the **This is a partial trust application** option button.
+
+5. Select **Advanced**.
+
+6. Select **Grant the application access to its site of origin**
+
+   If you select this check box, the application can access the website or server share on which it is published. By default, this option is selected.
+
+7. In the **Debug this application as if it were downloaded from the following URL** box, enter the URL.
+
+   If you need to allow the application to access the website or server share corresponding to the **Installation URL** you specified on the **Publish** page, enter that URL here.
+
 ## Related content
 
 - [Secure ClickOnce applications](../deployment/securing-clickonce-applications.md)

docs/deployment/how-to-install-prerequisites-with-a-clickonce-application.md

@@ -3,6 +3,8 @@ title: Install prerequisites with a ClickOnce app
 description: Select the appropriate prerequisite components for your configuration to package along with your ClickOnce application during installation.
 ms.date: 11/04/2016
 ms.topic: how-to
+f1_keywords:
+- Microsoft.VisualStudio.Publish.BaseProvider.Dialog.Bootstrapper
 dev_langs: 
   - VB
   - CSharp
@@ -40,6 +42,8 @@ All ClickOnce applications require that the correct version of the .NET Framewor
 
 3. Click the **Prerequisites** button to open the **Prerequisites** dialog box.
 
+   ![Screenshot of Prerequisites dialog box in Visual Studio.](media/prerequisites-dialog-box.png)
+
 4. In the **Prerequisites** dialog box, make sure that the **Create setup program to install prerequisite components** check box is selected.
 
 5. In the **Prerequisites** list, check the components that you wish to install, and then click **OK**.
@@ -65,4 +69,4 @@ All ClickOnce applications require that the correct version of the .NET Framewor
 
 ## Related content
 - [Publish ClickOnce applications](../deployment/publishing-clickonce-applications.md)
-- [How to: Publish a ClickOnce application using the Publish Wizard](../deployment/how-to-publish-a-clickonce-application-using-the-publish-wizard.md)
+- [How to: Publish a ClickOnce application using the Publish Wizard](../deployment/how-to-publish-a-clickonce-application-using-the-publish-wizard.md)

docs/deployment/how-to-specify-where-visual-studio-copies-the-files.md

@@ -1,8 +1,10 @@
 ---
 title: Specify ClickOnce Publish properties
 description: Learn how to set the Publish properties for a ClickOnce application, such as the location where the application files and manifest are put, and the installation URL.
-ms.date: 06/26/2024
+ms.date: 05/05/2025
 ms.topic: how-to
+f1_keywords:
+  - "Microsoft.VisualStudio.Publish.ClickOnceProvider.Dialog.PropertyPage"
 dev_langs: 
   - VB
   - CSharp
@@ -47,9 +49,9 @@ You can configure ClickOnce Publish properties on the **Publish** page of the **
 
 ## Specify a publishing location
 
-When you publish an application by using ClickOnce, the `Publish Location` property specifies the location where the application files and manifest are put. This can be a file path or the path to an FTP server.
+When you publish an application by using ClickOnce, the `Publish Location` property specifies the location where the application files and manifest are put. This can be a drive path (`C:\deploy\myapplication`), a file share (`\\server\myapplication`), or an FTP server (`ftp://ftp.microsoft.com/myapplication`). Note that text must be present in the **Publishing Location** box in order for the browse (**...**) button to work.
 
- You can specify the `Publish Location` property on the **Publish** page of the **Project Designer**, or by using the Publish Wizard. For more information, see [How to: Publish a ClickOnce Application using the Publish Wizard](../deployment/how-to-publish-a-clickonce-application-using-the-publish-wizard.md).
+You can specify the `Publish Location` property on the **Publish** page of the **Project Designer**, or by using the Publish Wizard. For more information, see [How to: Publish a ClickOnce Application using the Publish Wizard](../deployment/how-to-publish-a-clickonce-application-using-the-publish-wizard.md).
 
 > [!NOTE]
 > When you install more than one version of an application by using ClickOnce, the installation moves earlier versions of the application into a folder named Archive, in the publish location that you specify. Archiving earlier versions in this manner keeps the installation directory clear of folders from the earlier version.
@@ -118,6 +120,10 @@ The ClickOnce `Publish Version` property determines whether or not the applicati
 
 The `Publish Version` property can be set on the **Publish** page of the **Project Designer**.
 
+When the version number is changed, the application is published as an update. Each part of the publish version (**Major**, **Minor**, **Build**, **Revision**) can have a maximum value of 65535 (<xref:System.UInt16.MaxValue>), the maximum allowed by <xref:System.Version>.
+
+When you install more than one version of an application by using ClickOnce, the installation moves earlier versions of the application into a folder named Archive, in the publish location that you specify. Archiving earlier versions in this manner keeps the installation directory clear of folders from the earlier version.
+
 > [!NOTE]
 > There's a project option that will automatically increment the `Publish Version` property each time the application is published; this option is enabled by default. For more information, see [Automatically Increment the ClickOnce Publish Version](../deployment/how-to-specify-where-visual-studio-copies-the-files.md#automatically-increment-the-clickonce-publish-version).
 

docs/deployment/how-to-use-clickonce-to-deploy-applications-that-can-run-on-multiple-versions-of-the-dotnet-framework.md

@@ -18,7 +18,7 @@ ms.subservice: deployment
 ---
 # Use ClickOnce to deploy applications that can run on multiple versions of the .NET Framework
 
-You can deploy an application that targets multiple versions of the .NET Framework by using the ClickOnce deployment technology. This requires that you generate and update the application and deployment manifests.
+You can deploy an application that targets multiple versions of the .NET Framework by using the ClickOnce deployment technology. This task requires that you generate and update the application and deployment manifests.
 
 > [!NOTE]
 > Before you change the application to target multiple versions of the .NET Framework, you should ensure that your application runs with multiple versions of the .NET Framework. The version common language runtime is different between .NET Framework 4 versus .NET Framework 2.0, .NET Framework 3.0, and .NET Framework 3.5.
@@ -39,7 +39,7 @@ You can deploy an application that targets multiple versions of the .NET Framewo
 
 ### To generate the application and deployment manifests
 
-- Use the Publish Wizard or the Publish Page of the Project Designer to publish the application and generate the application and deployment manifest files. For more information, see [How to: Publish a ClickOnce application using the Publish Wizard](../deployment/how-to-publish-a-clickonce-application-using-the-publish-wizard.md) or [Publish Page, Project Designer](../ide/reference/publish-page-project-designer.md).
+- Use the Publish Wizard or the Publish Page of the Project Designer to publish the application and generate the application and deployment manifest files. For more information, see [How to: Publish a ClickOnce application using the Publish Wizard](../deployment/how-to-publish-a-clickonce-application-using-the-publish-wizard.md) or [Specify ClickOnce Publish properties](../deployment/how-to-specify-where-visual-studio-copies-the-files.md).
 
 [!INCLUDE[ndptecclick](../deployment/includes/dotnet-publish-tool.md)]
 
@@ -78,13 +78,13 @@ You can deploy an application that targets multiple versions of the .NET Framewo
 
 1. In the publish directory, open the application manifest by using the XML Editor in Visual Studio. The deployment manifest has the *.manifest* file name extension.
 
-2. Add `group="framework"` to the dependency XML for the sentinel assemblies (`System.Core`, `WindowsBase`, `Sentinel.v3.5Client`, and `System.Data.Entity`). For example, the XML should look like the following:
+2. Add `group="framework"` to the dependency XML for the sentinel assemblies (`System.Core`, `WindowsBase`, `Sentinel.v3.5Client`, and `System.Data.Entity`). The XML should appear similar to the following example:
 
    ```xml
    <dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true" group="framework">
    ```
 
-3. Update the version number of the `<assemblyIdentity>` element for Microsoft.Windows.CommonLanguageRuntime to the version number for the .NET Framework that is the lowest common denominator. For example, if the application targets .NET Framework 3.5 and .NET Framework 4, use the 2.0.50727.0 version number and the XML should look like the following:
+3. Update the version number of the `<assemblyIdentity>` element for Microsoft.Windows.CommonLanguageRuntime to the version number for the .NET Framework that is the lowest common denominator. For example, if the application targets .NET Framework 3.5 and .NET Framework 4, use the 2.0.50727.0 version number and the XML should appear as follows:
 
    ```xml
    <dependency>

docs/ide/reference/media/prerequisites-dialog-box.png renamed to docs/deployment/media/prerequisites-dialog-box.png

@@ -6,6 +6,7 @@ ms.topic: "conceptual"
 f1_keywords:
   - "Microsoft.VisualStudio.Publish.ClickOnceProvider.Dialog.Options"
   - "Microsoft.VisualStudio.Publish.ClickOnceProvider.PublishWizard.Help"
+  - "Microsoft.VisualStudio.Publish.ClickOnceProvider.Dialog.PropertyPage"
 dev_langs:
   - "VB"
   - "CSharp"
@@ -60,7 +61,7 @@ When publishing a ClickOnce application for the first time, publish properties c
  To include files, exclude files, mark files as data files or prerequisites, and create groups of files for conditional installation in the Visual Studio UI, see [How to: Specify which files are published by ClickOnce](../deployment/how-to-specify-which-files-are-published-by-clickonce.md). You can also mark data files by using the Mage.exe. For more information, see [How to: Include a data file in a ClickOnce application](../deployment/how-to-include-a-data-file-in-a-clickonce-application.md).
 
 ### Prerequisites dialog box
- This dialog box specifies which prerequisite components are installed, as well as how they are installed. For more information, see [How to: Install prerequisites with a ClickOnce application](../deployment/how-to-install-prerequisites-with-a-clickonce-application.md) and [Prerequisites dialog box](../ide/reference/prerequisites-dialog-box.md).
+ This dialog box specifies which prerequisite components are installed, as well as how they are installed. For more information, see [How to: Install prerequisites with a ClickOnce application](../deployment/how-to-install-prerequisites-with-a-clickonce-application.md).
 
 ### Application Updates dialog box
  This dialog box specifies how the application installation should check for updates. For more information, see [How to: Manage updates for a ClickOnce application](../deployment/how-to-manage-updates-for-a-clickonce-application.md).

docs/deployment/publishing-clickonce-applications.md

@@ -4,6 +4,9 @@ description: Explore the signing requirements to publish ClickOnce application a
 ms.date: 6/13/2024
 ms.subservice: deployment
 ms.topic: conceptual
+f1_keywords:
+- vb.ProjectPropertiesSigning
+- vb.ProjectPropertiesSigning.PfxPasswordDialog
 helpviewer_keywords:
 - manifests [Visual Studio]
 - code signing [Visual Studio], Authenticode
@@ -23,12 +26,12 @@ If you want to publish an application by using ClickOnce deployment, the applica
 
 The information in this article applies only if you're using the .NET Framework 4.8.1 or earlier. If you're using .NET 5 or later, follow the steps in [Deploy a .NET Windows desktop application using ClickOnce](../deployment/quickstart-deploy-using-clickonce-folder.md).
 
-For more information about ClickOnce deployment, see [ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md).
-
 Signing the ClickOnce manifests is optional for *.exe*-based applications. For more information, see the "Generate unsigned manifests" section of this document.
 
 For information about creating key files, see [How to: Create a public-private key pair](/dotnet/framework/app-domains/how-to-create-a-public-private-key-pair).
 
+For information about signing assemblies and application manifests, see [Manage assembly and manifest signing](../ide/managing-assembly-and-manifest-signing.md).
+
 > [!NOTE]
 > Visual Studio supports only Personal Information Exchange (PFX) key files that have the *.pfx* extension. However, you can select other types of certificates from the current user's Windows certificate store by clicking **Select from Store** on the **Signing** page of project properties.
 

docs/ide/how-to-sign-application-and-deployment-manifests.md

@@ -4,6 +4,12 @@ description: Explore how to manage an assembly and the advantages of strong-name
 ms.date: 07/18/2024
 ms.subservice: deployment
 ms.topic: conceptual
+f1_keywords:
+- vs.AddNewStrongNameKey
+- ResolveKeySource.KeyFileForSignAssemblyNotImported
+- vb.ProjectPropertiesSigning.ChangePasswordDialog
+- ResolveKeySource.KeyFileForManifestNotImported
+- vb.ProjectPropertiesSigning.PasswordNeededDialog
 helpviewer_keywords:
 - manifests [Visual Studio]
 - signing manifests [Visual Studio]
@@ -73,9 +79,8 @@ You can also point to a key you have already created. For more information about
 
 If you only have access to a public key, you can use delay-signing to defer assigning the key. You enable delay signing by selecting the **Delay sign only** check box. A delay-signed project doesn't run, and you can't debug it. However, you can skip verification during development by using the [Sn.exe strong name tool](/dotnet/framework/tools/sn-exe-strong-name-tool) with the `-Vr` option.
 
-For information about signing manifests, see [How to: Sign application and deployment manifests](../ide/how-to-sign-application-and-deployment-manifests.md).
-
 ## Related content
 
 - [Strong-named assemblies](/dotnet/framework/app-domains/strong-named-assemblies)
 - [Strong-named assemblies (C++/CLI)](/cpp/dotnet/strong-name-assemblies-assembly-signing-cpp-cli)
+- [How to: Sign application and deployment manifests](../ide/how-to-sign-application-and-deployment-manifests.md)