Forum Discussion
Windows Application Packaging Project - cannot select code signing certificate
Thanks TIMOTHY_MANGAN Is it just me or does anyone else think it's nuts that there are no specs for public signing certificates for MSIX and that the tooling give you no indication of what's wrong when it doesn't work.
Mike_Yeager Hello Mike, I was wondering if you found a solution? I am facing the same issue and even though I shared my screen with the support staff of ssl.com while going through each step, they claim that the certificates are ok. I am missing Basic Constraints as well.
itoinbgb Unfortunately no updates from Microsoft. It does work if you run the signing tools manually, but not through VS.
Mike_Yeager I am using signtool as a workaround for msix bundles (appinstaller format), like this:
"C:\Program Files (x86)\Windows Kits\10\bin\10.0.22000.0\x64\signtool.exe" sign /fd SHA256 /tr http://ts.ssl.com /td sha256 /a /f "path_toCertificate\certificate.pfx" /p ******** "PathToPackage\Package.msixbundle"This works fine for msixbundle, and for individual msix packages, I am using MSIX Packaging Tool:
I do hope this gets resolved eventually though, because this adds an additional step in the build process. Probably should buy another certificate from a CA that includes Basic Constraints.
- I would suggest that you try manually signing the unsigned output package using the signtool utility. This should provide better information on the issue. It would also probably force you to understand the password protection as the cert file ***SHOULD*** be password protected and you'll need that password to sign.
Also be careful to re-review whatever instructions you have on which store to put that cert and what folders (or whatever they are called) within the store. Sometimes I've had to use the system store and sometimes the user store. Sometimes the Trusted Roots folder, and sometimes Personal.- Hi @Timothy. We have established that we can manually sign using signtool. The issue is with Visual Studio. The Basic Constraints requirement is only from within Visual Studio. Last I heard the VS team was going to look into it.
