Reputation: 5024
At our company we use clickonce deployment for the client part of our client/server application. Clickonce package is deployed to an IIS server with FrontPage extensions installed. We do our compiling, signing and publishing to IIS directly from Visual Studio 2010. Our clickonce package is set up so that it check for newer version at each application startup.
The application has ~100 users@remote machines. Lately, when we publish the latest release some of the clients (about 10-15%) end up still using the old release. When we connect remotely to one of the clients and start the application we see that the clickonce launcher checks for a newer version and then starts the application without updating. We then have to uninstall the application and install it again via the clickonce-generated webpage in order to get the latest version.
Any ideas why this is happening and how can we prevent it? Is there any way to enable logging, to see why the launcher isn't picking up a newer version even though it checks for it at application startup?
Upvotes: 1
Views: 2910
Reputation: 12938
Run Fiddler and launch the app on one of the machines that isn't working. Verify it's checking for updates at the correct location and the update call is succeeding.
Upvotes: 1
Reputation: 397
I have two options you may want to try that my team uses on some of our deployments depending on the need. These may not suit your need exactly as they each have caveats, but should solve your problem.
Set "The applications is available online only" in the Publish settings. (Default is offline mode which installs to windows like a normal program) This mode re-downloads the application at each launch from the publish.html, and does not install it in windows. You have to launch the html or setup.exe each time. We get around the annoyance of this by making "menu" applications that just have a bunch of buttons/links that point to the applications we have out there in online modes so the users can find them.
If you still want to stick with offline mode like normal try setting the minimum required version = the current version. This should force ClickOnce to get that latest version each time, this seems to work for me, but I have not thoroughly tested this.
Upvotes: 0