ClickOnce Expired Certificate
Damn it!
I've got an upgrade I wanted to make to Comicster this weekend, and only now I've realised that the self-generated certificate I was using to sign the application has expired!
What does this mean for Comicster users? Well, I'm fairly certain it means that upgrades from the current version won't work. ClickOnce will assume that this new version, since it's signed with a different certificate, is a different program.
If I don't hear back from the MSDN forums with a decent solution, I'll have no option but to generate a new key and try to let everyone know to uninstall their current version and install the new one, rather than relying on the upgrade process.
What a bummer!!!
If you've had any experience with renewing expired self-generated certificates (or generating a new one with the same key), then please leave me a comment!
Comments
# anonymous
3/03/2007 1:13 AM
probably long since resolved, but check http://support.microsoft.com/?kbid=925521 for resolution.
# Bruce H
15/03/2007 4:32 AM
There's nothing you can do about an expired certificate. I was reading somewhere that the way to generate a long-lived "test certificate" is to set your computer clock forward (to, say, 2036) and then generate a test key from inside visual studio. That way it won't expire. This is not something MSDN is likely to mention.
# Saurabh
26/03/2007 11:12 AM
This issue has been fixed in the Orcas release of ClickOnce. The Beta1 of Orcas stated to be released soon will have this fix.
# mabster
26/03/2007 11:27 AM
Good to know, Saurabh! Thanks for the comment!
# naysh
18/02/2010 11:00 PM
Apparently mageUI can be used to overcome this issue just resign the app-manifest with mageui.exe