Published updates no longer downloading - problem with signing?

[Mateus]

Hi All,

I'm completely lost with signing and publishing, I feel like giving up.

My hard drive crashed recently and I had to reinstall everything. Thankfully I'd backed up my work but something's gone wrong with the project signing/certificates - I had to create a new certificate. Also, now when I publish, my clients don't get the updates (the My.Application.Deployment.Update() thread doesn't seem to be working anymore).

Users have to manually install the program from disk which is a real pain.

As I said, I'm lost as to how to restore this functionality. Any ideas?

Many thanks!
M.

Update: Just realised it's about 1 year since I started the project. Do VB.net Express 2008 cert's only last 1 year!?

 

[JohnH]

This sounds like a relevant article: Certificate Expiration in ClickOnce Deployment

 

[Mateus]

Thanks JohnH, since my post I had come across the site you linked to but I wanted to be sure this was the cause of my problems. I didn't receive a cert expired warning; just a warning that the cert was "different".

Oh well, at least reinstalling the application seems to resolve the problem.

M.

 

[JohnH]

It appeared to me that was basically the same scenario, though according to the article changing certificate with .Net 4 that you use shouldn't be a problem so perhaps it's something else.