Prev: Backup SQL Database Through Code In VB.NET
Next: Vb.net 2008 ContextMenuStrip logical error when running code
From: BillE on 17 Mar 2010 13:34 I think I'm forced to digitally sign my ClickOnce manifest and assembly for a windows forms application (see yesterday's post, 'click once deployment cannot continue'. This seems like a stupid question, but in all the articles I've read, I can't find what happens to a user when the digital certificate expires. Does the application just fail? Am i going to be scrambling to acquire a new certificate and publish updates signed with the new certificate? Will the application automatically update to the new version with the new certificate, once it is published?
From: Mr. Arnold on 17 Mar 2010 17:28
BillE wrote: > I think I'm forced to digitally sign my ClickOnce manifest and assembly for > a windows forms application (see yesterday's post, 'click once deployment > cannot continue'. > > This seems like a stupid question, but in all the articles I've read, I > can't find what happens to a user when the digital certificate expires. > > Does the application just fail? I don't know, but I suspect it would fail at some point, because it doesn't have a valid certificate. > Am i going to be scrambling to acquire a new certificate and publish updates > signed with the new certificate? > Will the application automatically update to the new version with the new > certificate, once it is published? > I thought certificates were at the machine level. So it seems that the user's workstation must be updated manually by the user. |