.NET Windows Forms Application Update Deployment
Question
We have an inner corporation Windows Forms application on .NET 4.0. Our problem is, some of the users are having troubles while updating the application because it is already installed.
The way that we publish the application is:
- Go to properties of the project
- Set new version to the application, set the update URL of the application.
- Publish the app to local.
- Deploy the app to the update URL.
By this, application always checks if a new version is deployed, and if so, it downloads and installs it.
As I said, our problem is that some of the users cannot install the application update properly and the app crashes. Then, we tell the users to uninstall the program and download the setup packege from the deployment place (Actually, as we couldn't fix the program, we had to write another application that does that!).
As it is not the same for all the users, I can't understand why this happens. One of our developers insists that this is a network related problem, but I wonder if we can set an absolute solution for that.
Why does this not work? How to fix it?
2 answers
solution1
1 2014-10-14 12:50:44
There is a another way for your problem. You should maintain version and update table user vise at database side. when user log in it will check the version on server and also current version if its differ. just a batch file with commands run for updation of particular executable.
solution2
1 2014-10-14 15:24:59
You must find the details why the particular installation has failed from the log of ClickOnce installations. It is by default in "Temporary internet folder". See the answer here or article here . You must definitely see the cause in the log file to troubleshoot it.
Usually it is OK to uninstall the application from Control panel and then install anew from the same URL or UNC path. Also it could be necessary to clear ClickOnce application cache %userprofile%\\Local Settings\\Apps\\2.0 .
Click once usually works well with smaller applications, from my experience problems happen more often with bigger apps with many libraries.
I am afraid that "an absolute solution" would be not to use click once deployment method.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.