1

I have been trying to sign the AppX generated by the D.A.C. in order to verify it works as expected, but it seems a self signed certificate is not enough.

I also tried to sign using my Comodo SHA256 certificate, but even if I make sure to use the same publisher name as the certificate in the manifest, I get 

SignTool Error: An unexpected internal error has occurred.
Error information: "Error: SignerSign() failed." (-2147024885/0x8007000b)

I am starting to wonder if this does not mean I have to use Authenticode.

I would very much appreciate advice about what should be done by others who have succeeded.

Stefan Wick MSFT
  • 13,600
  • 1
  • 32
  • 51
Mitch Match
  • 339
  • 4
  • 14

1 Answers1

0

I have been trying to sign the AppX generated by the D.A.C. in order to verify it works as expected, but it seems a self signed certificate is not enough.

We can use the -Sign flag when running the DAC to automatically sign your .appx package. Please see the details in Sign your converted desktop app

To deply the converted app, please notice the certificate should be installed on this machine, see my answer in Installation Failed after creating UWP with Desktop App Converter

I am starting to wonder if this does not mean I have to use Authenticode

Yes, the Authenticode programs include MakeCert, see here

------------Update(09/25/2016)-----------

Deploy your application using the add-appxpackage –register AppxManifest.xml cmdlet or by repackaging it using MakeAppx, see App packager (MakeAppx.exe)

Please locate to the Appx layout folder which contains AppxManifest.xml file, after updating this file to contain a reference to the VCLibs UWPDesktop framework package, open Powershell(as Administrator) and type:

add-appxpackage –register AppxManifest.xml

Note: if the package has been installed on this device, please uninstall it first, otherwise you will see the conflict exception

Community
  • 1
  • 1
Franklin Chen - MSFT
  • 4,845
  • 2
  • 17
  • 28
  • I tried the -Sign option but yet, the AppC cannot run. – Mitch Match Sep 24 '16 at 17:18
  • @MitchMatch what's the meaning of "can not run"?how did you deploy – Franklin Chen - MSFT Sep 24 '16 at 17:19
  • I simply double click on the AppX and click Install. – Mitch Match Sep 24 '16 at 17:23
  • @MitchMatch then you could install the package on your machine? – Franklin Chen - MSFT Sep 24 '16 at 17:24
  • No, I could not install, it says I have to get in touch with the developer. I am now reading your page about using the AppX with a self-signed certificate. I am going to follow it step by step. Thank you. – Mitch Match Sep 24 '16 at 17:26
  • @MitchMatch all right, please follow my steps to install the certificate, then you can install the appx smoothly – Franklin Chen - MSFT Sep 24 '16 at 17:28
  • New hurdle. After following your guidelines, I get this when I tried to launch: Ask the developer for a new app package. This package may conflict with a package already installed, or it depends on things not installed here (package dependencies), or is made for a different architecture (0x80073CF3) – Mitch Match Sep 24 '16 at 17:59
  • I reran the converter, and indeed there is an issue with dependencies: Warning Summary: W_PACKAGE_DEPENDENCY_ADDED A dependency on framework package 'Microsoft.VCLibs.120.00.UWPDesktop' was added to the AppxManifest.xml. See 'http://go.microsoft.com/fwlink/?LinkId=821959' for guidance on installing the package prior to local deployment. Otherwise, if this is in error, remove the corresponding entry from Dependencies in the AppxManifest.xml before packaging and deploying your application. – Mitch Match Sep 24 '16 at 18:05
  • @MitchMatch please follow the steps: Referencing the VC Runtime framework packages from converted desktop apps in that blog https://blogs.msdn.microsoft.com/vcblog/2016/07/07/using-visual-c-runtime-in-centennial-project/ – Franklin Chen - MSFT Sep 24 '16 at 18:09
  • Alright. I see. Will follow that scrupulously. Thank you Franklin. You advanced me greatly. – Mitch Match Sep 24 '16 at 18:26
  • Confused by this sentence : "Deploy your application using the add-appxpackage –register AppxManifest.xml cmdlet or by repackaging it using MakeAppx, see App packager (MakeAppx.exe). – Mitch Match Sep 24 '16 at 18:48
  • Does it mean I should launch my existing converted AppX from the command line with the add -appxpackage option ? How ? – Mitch Match Sep 24 '16 at 18:49
  • 1
    @MitchMatch Please see my updated answer **Update(09/25/2016)** – Franklin Chen - MSFT Sep 25 '16 at 06:43