Corrupt VB.net ClickOnce Deployment
Posted on 2010-11-17
I have a VB.NET (Built in VS 2008 SP1) ClickOnce Deployment. I am no expert in the ClickOnce technology, but have been able to successfully deploy 1 application on our internal network to about 100 machines.
We recently had an issue where one of the published manifests (I think) on the server was accidentally opened (in Notepad) by someone which broke the signing/security. Then, every time a client ran the application (to get the auto-update) many errors occurred (which I did not save unfortunately).
Eventually, I restored from backup the network setup files to the server and that 'fixed' the issue.
Does anyone have an explanation of the role of these manifests in the application:
I am guessing it is a no-no to edit these files directly - which is what caused the original problem.
What would be the procedure to Re-Deploy the application if did 'break'?
1) Uninstall the application at the client machine
2) Re-Publish a new Application to a new network location.
3) Re-install from this new publish location?
I am trying to do some disaster preparedness for any potential roadblocks.... I would appreciate any direction from the Experts!