Step 2: Create a private key using MakeCert.exe Copy and paste the string where possible. The Publisher attribute string that is defined for the Identity element in the AppxManifest.xml must be identical to the string that you specify with the MakeCert /n parameter for the certificate subject name. This parameter string is specified in quotes and is both case and whitespace sensitive. For example, suppose the AppxManifest.xml contains: įor the publisherName parameter that you specify with the MakeCert utility in the next step, use "CN=Contoso Software, O=Contoso Corporation, C=US". To make the signing certificate that you create usable with the app package that you want to sign, the subject name of the signing certificate must match the Publisher attribute of the Identity element in the AppxManifest.xml for that app.
Instructions Step 1: Determine the publisher name of the package MakeCert.exe and Pvk2Pfx.exe tools from the WDK.
Then you can use the certificates to sign the app packages, so they can be deployed locally for testing. You can create certificates by using MakeCert.exe and Pvk2Pfx.exe from the Windows Driver Kit (WDK). If you don't use Microsoft Visual Studio 2012 to create and sign your app packages, you need to create and manage your own code signing certificates. You must digitally sign your packaged Windows apps before you deploy them. Learn how to use MakeCert.exe and Pvk2Pfx.exe to create a test code signing certificate, so that you can sign your Windows app packages. For current guidance on creating a certificate, see Create a certificate for package signing.
0 kommentar(er)
