The certificate you use to sign your ClickOnce deployment will expire at some point. In the past, creating or purchasing a new certificate and deploying an update to your application always required the customers to uninstall and reinstall the application. This is no longer always the case. This GoldMail summarizes this issue, and provides solutions if it is a problem for you.
This download contains the written article with details and sample code (VS2008, C#). If you are a VB developer and can’t figure out how to translate this to VB, post a query and I’ll see what I can do for you.
ClickOnce_ExpiringCerts.zip
July 16, 2009 at 5:52 pm |
Hi Robin. Do you happen to have a VB version of your “ClickOnce and Expiring Certificates” sample code?
July 19, 2009 at 9:29 pm |
I don’t, but I will write one and post it here w/i the next week.
October 20, 2009 at 7:35 am |
This could be incredibly handy for me. I’m trying to migrate all my users of one application to another in one easy movement.
My intention is to use a version of this code to uninstall their current application, and install the new application.
Question though, you use the IntPtr type in the C# code, how would this translate to VB.Net, since VB doesnt support pointers?
Thanks
Fergal
October 22, 2009 at 12:17 pm |
It IS incredibly useful for all kinds of things. I’m going to be posting the code in both C# and VB in the next few days, along with an updated version of the article and a flowchart that includes .NET 4.0. I’m hoping to have at least the code out there by the end of the weekend, and will add a link pointing to the new post from the old one, or add a link to the old one, or something like that.