What happens when ClickOnce Certificate expire?

[DineshVelupula]

Published a application at say 06-01-2006 with the ClickOnce
deployment. Before that we sign a own test certificate because the
application is only used internally.

After the 06-01-2007 when the certificate expire. The users will not
be able to start the application.

What should we do to prevent the users to uninstall the application
and reinstall it again?

 

[DineshVelupula]

Okay, The workaround is available at the KB site... you just need to
have VC++ installed, and you should be able to compile the code sample
in the article and run it on your cert.

http://support.microsoft.com/Default.aspx?kbid=925521

To answer another question: this is not going to be fixed in VS 2005
SP1, but a permanent fix is being worked on. There's no promises at
this time when, or if, we'll be able to release it, but be assured, we
understand the pain and are working on it.



I'm posting because we do have a solution available for people using
the "temporary" certificates created by Visual Studio. If you
published using one of these certificates (as I did with Bootstrapper
Manifest Generator), we have a small utility that can read in the
original certificate and output a new certificate with the same info
(private key I think) and a 5-year expiration. You can then sign your
update and it will work. As I understand it, this utility will NOT
work on certificates from Verisign and Thawte and others.