Refactor ClickOnce articles describing configuration in the Wizard (#11516)

* Refactor ClickOnce security settings

* removed files

* TOC updates

* link updates

* minor edit

* TOC updates

* TOC updates

* TOC updates

* tweak

* link fixes

* Correct typo: is display > is displayed

---------

Co-authored-by: Dennis Rea <[email protected]>

Author: Mikejo5000

.openpublishing.redirection.json

@@ -1,5 +1,35 @@
 {
   "redirections": [
+    {
+      "source_path": "docs/deployment/how-to-automatically-increment-the-clickonce-publish-version.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-set-the-clickonce-publish-version.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-specify-the-clickonce-offline-or-online-install-mode.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-specify-the-location-where-end-users-will-install-from.md",
+      "redirect_url": "/visualstudio/deployment/how-to-specify-where-visual-studio-copies-the-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-set-a-security-zone-for-a-clickonce-application.md",
+      "redirect_url": "/visualstudio/deployment/how-to-enable-clickonce-security-settings",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/deployment/how-to-set-custom-permissions-for-a-clickonce-application.md",
+      "redirect_url": "/visualstudio/deployment/how-to-enable-clickonce-security-settings",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/deployment/azure-deployment-using-github-actions.md",
       "redirect_url": "/visualstudio/azure/azure-deployment-using-github-actions",

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

@@ -92,9 +92,9 @@ ClickOnce applications are based on the .NET Framework and are subject to code a
 
 ## See also
 - [Secure ClickOnce applications](../deployment/securing-clickonce-applications.md)
-- [How to: Enable ClickOnce security settings](../deployment/how-to-enable-clickonce-security-settings.md)
-- [How to: Set a security zone for a ClickOnce application](../deployment/how-to-set-a-security-zone-for-a-clickonce-application.md)
-- [How to: Set custom permissions for a ClickOnce application](../deployment/how-to-set-custom-permissions-for-a-clickonce-application.md)
-- [How to: Debug a ClickOnce application with restricted permissions](securing-clickonce-applications.md)
+- [Enable and configure ClickOnce security settings](../deployment/how-to-enable-clickonce-security-settings.md)
+- [Set a security zone for a ClickOnce application](../deployment/how-to-enable-clickonce-security-settings.md#set-a-security-zone-for-a-clickonce-application)
+- [Set custom permissions for a ClickOnce application](../deployment/how-to-enable-clickonce-security-settings.md#set-custom-permissions-for-a-clickonce-application)
+- [Debug a ClickOnce application with restricted permissions](securing-clickonce-applications.md)
 - [Trusted application deployment overview](../deployment/trusted-application-deployment-overview.md)
 - [Security Page, Project Designer](../ide/reference/security-page-project-designer.md)

docs/deployment/how-to-add-a-trusted-publisher-to-a-client-computer-for-clickonce-applications.md

@@ -60,10 +60,10 @@ With Trusted Application Deployment, you can configure client computers so that
 - [Code access security for ClickOnce applications](../deployment/code-access-security-for-clickonce-applications.md)
 - [ClickOnce and Authenticode](../deployment/clickonce-and-authenticode.md)
 - [Trusted application deployment overview](../deployment/trusted-application-deployment-overview.md)
-- [How to: Enable ClickOnce security settings](../deployment/how-to-enable-clickonce-security-settings.md)
-- [How to: Set a security zone for a ClickOnce application](../deployment/how-to-set-a-security-zone-for-a-clickonce-application.md)
-- [How to: Set custom permissions for a ClickOnce application](../deployment/how-to-set-custom-permissions-for-a-clickonce-application.md)
-- [How to: Debug a ClickOnce application with restricted permissions](securing-clickonce-applications.md)
-- [How to: Add a trusted publisher to a client computer for ClickOnce applications](../deployment/how-to-add-a-trusted-publisher-to-a-client-computer-for-clickonce-applications.md)
-- [How to: Re-sign application and deployment manifests](../deployment/how-to-re-sign-application-and-deployment-manifests.md)
-- [How to: Configure the ClickOnce trust prompt behavior](../deployment/how-to-configure-the-clickonce-trust-prompt-behavior.md)
+- [Enable and configure ClickOnce security settings](../deployment/how-to-enable-clickonce-security-settings.md)
+- [Set a security zone for a ClickOnce application](../deployment/how-to-enable-clickonce-security-settings.md#set-a-security-zone-for-a-clickonce-application.md)
+- [Set custom permissions for a ClickOnce application](../deployment/how-to-enable-clickonce-security-settings.md#set-custom-permissions-for-a-clickonce-application)
+- [Debug a ClickOnce application with restricted permissions](securing-clickonce-applications.md)
+- [Add a trusted publisher to a client computer for ClickOnce applications](../deployment/how-to-add-a-trusted-publisher-to-a-client-computer-for-clickonce-applications.md)
+- [Re-sign application and deployment manifests](../deployment/how-to-re-sign-application-and-deployment-manifests.md)
+- [Configure the ClickOnce trust prompt behavior](../deployment/how-to-configure-the-clickonce-trust-prompt-behavior.md)

docs/deployment/how-to-automatically-increment-the-clickonce-publish-version.md

@@ -30,7 +30,7 @@ You can configure the ClickOnce trust prompt to control whether end users are gi
 
 |Option|Registry setting value|Description|
 |------------|----------------------------|-----------------|
-|Enable the trust prompt.|`Enabled`|The ClickOnce trust prompt is display so that end users can grant trust to ClickOnce applications.|
+|Enable the trust prompt.|`Enabled`|The ClickOnce trust prompt is displayed so that end users can grant trust to ClickOnce applications.|
 |Restrict the trust prompt.|`AuthenticodeRequired`|The ClickOnce trust prompt is only displayed if ClickOnce applications are signed with a certificate that identifies the publisher.|
 |Disable the trust prompt.|`Disabled`|The ClickOnce trust prompt is not displayed for any ClickOnce applications that are not signed with an explicitly trusted certificate.|
 
@@ -234,9 +234,9 @@ You can configure the ClickOnce trust prompt to control whether end users are gi
 - [Code access security for ClickOnce applications](../deployment/code-access-security-for-clickonce-applications.md)
 - [ClickOnce and Authenticode](../deployment/clickonce-and-authenticode.md)
 - [Trusted application deployment overview](../deployment/trusted-application-deployment-overview.md)
-- [How to: Enable ClickOnce security settings](../deployment/how-to-enable-clickonce-security-settings.md)
-- [How to: Set a security zone for a ClickOnce application](../deployment/how-to-set-a-security-zone-for-a-clickonce-application.md)
-- [How to: Set custom permissions for a ClickOnce application](../deployment/how-to-set-custom-permissions-for-a-clickonce-application.md)
-- [How to: Debug a ClickOnce application with restricted permissions](securing-clickonce-applications.md)
-- [How to: Add a trusted publisher to a client computer for ClickOnce applications](../deployment/how-to-add-a-trusted-publisher-to-a-client-computer-for-clickonce-applications.md)
-- [How to: Re-sign application and deployment manifests](../deployment/how-to-re-sign-application-and-deployment-manifests.md)
+- [Enable and configure ClickOnce security settings](../deployment/how-to-enable-clickonce-security-settings.md)
+- [Set a security zone for a ClickOnce application](../deployment/how-to-enable-clickonce-security-settings.md#set-a-security-zone-for-a-clickonce-application)
+- [Set custom permissions for a ClickOnce application](../deployment/how-to-enable-clickonce-security-settings.md#set-custom-permissions-for-a-clickonce-application)
+- [Debug a ClickOnce application with restricted permissions](securing-clickonce-applications.md)
+- [Add a trusted publisher to a client computer for ClickOnce applications](../deployment/how-to-add-a-trusted-publisher-to-a-client-computer-for-clickonce-applications.md)
+- [Re-sign application and deployment manifests](../deployment/how-to-re-sign-application-and-deployment-manifests.md)

docs/deployment/how-to-configure-the-clickonce-trust-prompt-behavior.md

@@ -1,7 +1,7 @@
 ---
-title: Enable ClickOnce Security Settings | Microsoft Docs
+title: Enable & configure ClickOnce security | Microsoft Docs
 description: Learn how the Publish wizard automatically enables code access security for ClickOnce applications to publish the application.
-ms.date: 11/04/2016
+ms.date: 08/04/2023
 ms.topic: how-to
 dev_langs: 
   - VB
@@ -19,18 +19,21 @@ ms.technology: vs-ide-deployment
 ms.workload: 
   - multiple
 ---
-# How to: Enable ClickOnce security settings
+# How to: Enable and configure ClickOnce security settings in Visual Studio
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
-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.
-
- 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.
 
- ClickOnce security settings can be enabled or disabled on the **Security** page of the **Project Designer**.
+You can enable and configure ClickOnce security settings in the **Security** page of the **Project Designer**. In this article, you learn how to enable security settings, configure security zones, and configure customized security zones.
 
  [!INCLUDE[ndptecclick](../deployment/includes/dotnet-task-unsupported.md)]
 
-### To enable ClickOnce security settings
+## 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.
+
+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.
+
+ClickOnce security settings can be enabled or disabled on the **Security** page of the **Project Designer**.
 
 1. With a project selected in **Solution Explorer**, on the **Project** menu, click **Properties**.
 
@@ -56,6 +59,54 @@ Code access security for ClickOnce applications must be enabled in order to publ
     > [!NOTE]
     > Each time the application is published with the Publish wizard, this check box will be selected; you must clear it again after each successful publish.
 
+## Set a security zone for a ClickOnce application
+
+When setting code access security permissions for a ClickOnce application, you need to start with a base set of permissions on the **Security** page of the **Project Designer**.
+
+In most cases, you can also choose the **Internet** zone which contains a limited set of permissions, or the **Local Intranet** zone which contains a greater set of permissions. If your application requires custom permissions, you can do so by choosing the [Custom security zone](#set-custom-permissions-for-a-clickonce-application).
+
+### To set a security 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.
+
+     The controls in the **ClickOnce security permissions** section are enabled.
+
+5. In the **Zone your application will be installed from** drop-down list, select a security zone.
+
+## Set custom permissions for a ClickOnce application
+
+You can deploy a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application that uses default permissions for the Internet or Local Intranet zones. Alternatively, you can create a custom zone for the specific permissions that the application needs. You can do this by customizing the security permissions on the **Security** page of the **Project Designer**.
+
+### To customize a permission
+
+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.
+
+     The controls in the **ClickOnce security permissions** section are enabled.
+
+5. From the **Zone your application will be installed from** drop-down list, click **(Custom)**.
+
+6. Click **Edit Permissions XML**.
+
+     The *app.manifest* file opens in the XML Editor.
+
+7. Before the `</applicationRequestMinimum>` element, add XML code for permissions that your application requires.
+
+    > [!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.
+
 ## See also
+
 - [Secure ClickOnce applications](../deployment/securing-clickonce-applications.md)
 - [Code access security for ClickOnce applications](../deployment/code-access-security-for-clickonce-applications.md)

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

@@ -117,9 +117,9 @@ After you make changes to deployment properties in the application manifest for
 - [Code access security for ClickOnce applications](../deployment/code-access-security-for-clickonce-applications.md)
 - [ClickOnce and Authenticode](../deployment/clickonce-and-authenticode.md)
 - [Trusted application deployment overview](../deployment/trusted-application-deployment-overview.md)
-- [How to: Enable ClickOnce security settings](../deployment/how-to-enable-clickonce-security-settings.md)
-- [How to: Set a security zone for a ClickOnce application](../deployment/how-to-set-a-security-zone-for-a-clickonce-application.md)
-- [How to: Set custom permissions for a ClickOnce application](../deployment/how-to-set-custom-permissions-for-a-clickonce-application.md)
-- [How to: Debug a ClickOnce application with restricted permissions](securing-clickonce-applications.md)
-- [How to: Add a trusted publisher to a client computer for ClickOnce applications](../deployment/how-to-add-a-trusted-publisher-to-a-client-computer-for-clickonce-applications.md)
-- [How to: Configure the ClickOnce trust prompt behavior](../deployment/how-to-configure-the-clickonce-trust-prompt-behavior.md)
+- [Enable and configure ClickOnce security settings](../deployment/how-to-enable-clickonce-security-settings.md)
+- [Set a security zone for a ClickOnce application](../deployment/how-to-enable-clickonce-security-settings.md#set-a-security-zone-for-a-clickonce-application)
+- [Set custom permissions for a ClickOnce application](../deployment/how-to-enable-clickonce-security-settings.md#set-custom-permissions-for-a-clickonce-application)
+- [Debug a ClickOnce application with restricted permissions](securing-clickonce-applications.md)
+- [Add a trusted publisher to a client computer for ClickOnce applications](../deployment/how-to-add-a-trusted-publisher-to-a-client-computer-for-clickonce-applications.md)
+- [Configure the ClickOnce trust prompt behavior](../deployment/how-to-configure-the-clickonce-trust-prompt-behavior.md)