Merge pull request #12816 from MicrosoftDocs/ghogen-patch-59

Review and update

Author: prmerger-automator[bot]

docs/ide/managing-assembly-and-manifest-signing.md

@@ -1,7 +1,7 @@
 ---
 title: Manage assembly and manifest signing
 description: Explore how to manage an assembly and the advantages of strong-name signing, which gives a software component a globally unique identity. 
-ms.date: 04/17/2024
+ms.date: 07/18/2024
 ms.subservice: deployment
 ms.topic: conceptual
 helpviewer_keywords:
@@ -56,7 +56,9 @@ For .NET Core (and .NET 5 and later) C# projects in Visual Studio 2022:
 
 1. Open the project properties window (right-click the project node in **Solution Explorer** and select **Properties**).
 1. Under **Build**, look for **Strong naming**, and select the **Sign the assembly** checkbox. Additional options for the key file and delay signing appear when you check the box.
-1. Specify a key file. If you choose to create a new key file, new key files are always created in the *.pfx* format. You need a name and password for the new file.
+1. Specify a key file.
+
+If you don't have a key file, you can use the command line to [create an `.snk` file](/dotnet/standard/assembly/create-public-private-key-pair). You can also use or generate a certificate in a `.pfx` file using the **Publish** process, and in the **Sign manifests** step, you can create a test certificate to use only during development and testing, or for production, use a certificate issued by your IT department or by an authorized source. See [Deploy a .NET Windows Desktop app with ClickOnce](../deployment/quickstart-deploy-using-clickonce-folder.md).
 
 For .NET Framework and Visual Basic projects in Visual Studio 2022, or in Visual Studio 2019: