Click here to Skip to main content
15,885,782 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
My software development computer is getting upgraded from Win 7 to Win 10. I use Click Once to deploy all my applications and I have created a Certificate to do so using MakeCert. I have been able to export my cert to my new box and I can see it in my project, however, I am not able to run any program with that certificate on the Win 10 box as it gives me an error saying my certificate is not valid for signing.

I remember several years ago that MS released an update that required the key in my certificate to be a certain length. To get around that issue, we ended up removing the update and everything worked. I am wondering if this is the same issue I am having now. I went back and found the update number for that change but I can't find it anywhere on my Win 10 box. I am wondering if this feature is now just built into Win 10 and there is no way to have a Cert other then with a long key? Can anyone confirm this or not?

What I have tried:

Most of my apps are in either VS2005 or VS2015 so most of them are targeting DotNet 2.0. and I am trying to figure out the best way forward. I found this article online about creating an app that uninstalls and resinstalls with a new certificate but I am not sure if that is my best solution or not.

Certificate Expiration in ClickOnce Deployment | Microsoft Docs[^]
Posted
Comments
[no name] 20-Oct-20 14:34pm    
Get a new cert ... How much life energy have you spent avoiding that?

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900