I am going mental in trying to find a solution to sign a ClickOnce manifest of a simple desktop app in Visual Studio 2022. I have a new standard code signing certificate issued after June 2023 (i.e., USB token).
Every time I click on "Publish" and then select "Sign the ClickOnce Manifest" and "Select from Store", I get the error "No Certificates Were Found That Met All the Given Criteria".
Any idea why? Or, is there any workaround/different process I can follow to sign the manifest?
I tried signing different manifests from different apps and I am getting the same error. Signing code using SignTool works without problem.
2
Answers
If you are using .net framework:
Project properties=>signing=>Create Test Certificate
If this doesn’t work for you, you can refer to: Signtool error: No certificates were found that met all given criteria with a Windows Store App?
I have had the same problem after my certificate expired, last year. As I understand, from June 2023, the code signing requires more stringent procedure than before and that the most CA’s opted for an USB-token based solution. I decided to start using Certum certificates that are much cheaper (120 Euro) and do not require a physical token. Instead, signing works with a phone app and the local certificate store. From the users perspective it appears working from the certificate store. I have no idea how their solution actually works, but it works just fine (I’m signing my C# desktop application directly from Visual Studio 2022)