Merge pull request #8459 from MicrosoftDocs/main637986350623520407sync_temp

Repo sync for protected CLA branch

Author: Court72

docs/get-started/visual-basic/index.yml

@@ -8,7 +8,7 @@ metadata:
   description: Create Visual Basic apps by using Visual Studio.
   ms.custom: vs-acquisition
   ms.topic: landing-page
-  ms.date: 06/19/2021
+  ms.date: 09/01/2022
   ms.author: ghogen
   author: ghogen
   manager: jmartens

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

@@ -1,8 +1,7 @@
 ---
 title: 'How to: Sign application and deployment manifests'
 description: Learn about requirements for signing for publishing ClickOnce application and deployment manifests. Signing is optional for .exe-based applications.
-ms.custom: SEO-VS-2020
-ms.date: 11/04/2016
+ms.date: 09/12/2022
 ms.technology: vs-ide-deployment
 ms.topic: conceptual
 helpviewer_keywords:
@@ -27,6 +26,8 @@ ms.workload:
 
 If you want to publish an application by using ClickOnce deployment, the application and deployment manifests must be signed with a public/private key pair and signed using Authenticode technology. You can sign the manifests by using a certificate from the Windows certificate store or a key file.
 
+The information in this article applies only if you're using the .NET Framework 4.7.2 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.
@@ -38,50 +39,57 @@ For information about creating key files, see [How to: Create a public-private k
 
 ## Sign using a certificate
 
+To use this method, you must have a certificate signed by a certificate authority (CA). Certificates are issued by third-party certification service providers, or by authorized organizations within an Enterprise.
+
 1. Go to the project properties window (right-click the project node in **Solution Explorer** and select **Properties**). On the **Signing** tab, select the **Sign the ClickOnce manifests** check box.
 
-2. Click the **Select from Store** button.
+1. Click the **Select from Store** button.
 
      The **Select a Certificate** dialog box appears and displays the contents of the Windows certificate store.
 
     > [!TIP]
     > If you click **Click here to view certificate properties**, the **Certificate Details** dialog box appears. This dialog box includes detailed information about the certificate and additional options. Click **Certificates** to view additional help information.
 
-3. Select the certificate that you want to use to sign the manifests.
+1. Select the certificate that you want to use to sign the manifests.
 
-4. Additionally, you can specify the address of a timestamp server in the **Timestamp server URL** text box. This is a server that provides a timestamp specifying when the manifest was signed.
+   > [!TIP]
+   > If there aren't any certificates in the store, you can still [sign using a test certificate](#sign-using-a-test-certificate).
+
+1. Additionally, you can specify the address of a timestamp server in the **Timestamp server URL** text box. This is a server that provides a timestamp specifying when the manifest was signed. It's usually provided by the same third party that offers certificates signed by a CA.
 
 ## Sign using an existing key file
 
 1. On the **Signing** page, select the **Sign the ClickOnce manifests** check box.
 
-2. Click the **Select from File** button.
+1. Click the **Select from File** button.
 
      The **Select File** dialog box appears.
 
-3. In the **Select File** dialog box, browse to the location of the key file (*.pfx*) that you want to use, and then click **Open**.
+1. In the **Select File** dialog box, browse to the location of the key file (*.pfx*) that you want to use, and then click **Open**.
 
     > [!NOTE]
     > This option supports only files that have the *.pfx* extension. If you have a key file or certificate in another format, store it in the Windows certificate store and select the certificate is described in the previous procedure. The selected certificate's purpose should include code signing.
 
      The **Enter password to open file** dialog box appears. (If the *.pfx* file is already stored in your Windows certificate store or is not password protected, you aren't prompted to enter a password.)
 
-4. Enter the password to access the key file, and then select **Enter**.
+1. Enter the password to access the key file, and then select **Enter**.
 
 > [!NOTE]
 > The *.pfx* file cannot include certificate chaining information. If it does, the following import error will occur: **Cannot find the certificate and private key for decryption**. To remove the certificate chaining information, you can use *Certmgr.msc* and [disable the option](/previous-versions/aa730868(v=vs.80)) to **Include all certificates** when exporting the  *.pfx file.
 
 ## Sign using a test certificate
 
+Test certificates are not signed by a Certificate Authority (CA) and should only be used for testing purposes. For details on test certificates, see [How using certificates authorities helps users](../deployment/clickonce-and-authenticode.md#how-using-certificate-authorities-helps-users).
+
 1. On the **Signing** page, select the **Sign the ClickOnce manifests** check box.
 
-2. To create a new certificate for testing, click the **Create Test Certificate** button.
+1. To create a new certificate for testing, click the **Create Test Certificate** button.
 
-3. In the **Create Test Certificate** dialog box, enter a password to help secure your test certificate.
+1. In the **Create Test Certificate** dialog box, enter a password to help secure your test certificate.
 
 ## Generate unsigned manifests
 
-Signing the ClickOnce manifests is optional for *.exe*-based applications. The following procedures show how to generate unsigned ClickOnce manifests.
+Signing the ClickOnce manifests is optional for `.exe`-based applications. The following procedures show how to generate unsigned ClickOnce manifests.
 
 > [!IMPORTANT]
 > Unsigned manifests can simplify development and testing of your application. However, unsigned manifests introduce substantial security risks in a production environment. Only consider using unsigned manifests if your ClickOnce application runs on computers within an intranet that is completely isolated from the internet or other sources of malicious code.
@@ -90,24 +98,24 @@ By default, ClickOnce automatically generates signed manifests unless one or mor
 
 ### To generate unsigned manifests and include all files in the generated hash
 
-1. To generate unsigned manifests that include all files in the hash, you must first publish the application together with signed manifests. Therefore, first sign the ClickOnce manifests by following one of the previous procedures, and then publish the application.
+To generate unsigned manifests that include all files in the hash, you must first publish the application together with signed manifests. Therefore, first sign the ClickOnce manifests by following one of the previous procedures, and then publish the application.
 
-2. On the **Signing** page, clear the **Sign the ClickOnce manifests** check box.
+1. On the **Signing** tab, clear the **Sign the ClickOnce manifests** check box.
 
-3. Reset the publish version so that only one version of your application is available. By default, Visual Studio automatically increments the revision number of the publish version every time that you publish an application. For more information, see [How to: Set the ClickOnce publish version](../deployment/how-to-set-the-clickonce-publish-version.md).
+1. On the **Publish** tab, reset the publish version so that only one version of your application is available. Clear the checkbox for **Automatically increment the version with each publish**. By default, Visual Studio automatically increments the revision number of the publish version every time that you publish an application. For more information, see [How to: Set the ClickOnce publish version](../deployment/how-to-set-the-clickonce-publish-version.md).
 
-4. Publish the application.
+1. Publish the application. Visual Studio tells you that the application was signed with a different key than the existing application on the server, and asks if you want to overwrite it. Choose **Yes**.
 
 ### To generate unsigned manifests and exclude one or more files from the generated hash
 
 1. On the **Signing** page, clear the **Sign the ClickOnce manifests** check box.
 
-2. Open the **Application Files** dialog box and set the **Hash** to **Exclude** for the files that you want to exclude from the generated hash.
+1. On the **Publish** tab, choose the **Application Files** button to open the **Application Files** dialog box, and set the **Hash** to **Exclude** for the files that you want to exclude from the generated hash.
 
     > [!NOTE]
     > Excluding a file from the hash configures ClickOnce to disable automatic signing of the manifests, so you do not need to first publish with signed manifests as shown in the previous procedure.
 
-3. Publish the application.
+1. Publish the application.
 
 ## See also