Application Loader, Self-Update

Upgrade is a very painful process for desktop application in multi-users environment. We got to update latest EXE, fxp, dbf and etc to ALL user machine by running upgrade program or xcopy them manually.

Some time ago, VFP developers shared programs like "Application Loader" and "Application Updater" which automate the upgrade process. These programs check for any updated files available at LAN/Web server. If any, these files would be copied to local machine, register them if necessary.

With this, users no longer launch our application. Instead, user only launch Application Loader. Application Loader would update files and launch the actual EXE.

Application Loader should be a less maintainance program because we seldom change the logic. However, seldom change meant still got chance we need to change it. We may need to enhance or add more features to it. For example, current version doesn't support COM DLL registration. We wan to build this feature within next few months.

OK, now we back to our old problem. How are we going to update our Application Loader?

I borrowed Les Pinter idea to solve this problem.

Below is the flowchart of my self-update Application Loader.



I am using ShellExec API to launch instance of "latest" Application Loader so that "older" Application loader able to get back control and exit immediatelly.

If you have any comments or suggestions, pls email me. Thank you