wodAppUpdate 1.2.7

WodAppUpdate component should be used by your application to quickly, easily, and securely provide automatic update solution - very popular "check for updates" functionality. This way you increase value and functionality of your product because now your customers always have the most newest version - and you need only 3 lines of code to provide it! wodAppUpdate uses configuration file it finds on the server of your choice (HTTP, HTTPS or FTP) and then determines if local files need to be replaced or not. Works with any development tool capable of generating apps which can host an ActiveX control.
wodAppUpdate uses configuration file it finds on the server of your choice and then determines if local files need to be replaced or not.

You can send any additional information via URL to the server - and that way determine if user is allowed to update the application, if he uses regular licensed version etc - using your own server-side scripting. wodAppUpdate doesn't really care what you send and what do you do on the server side.

wodAppUpdate can be also used to provide "admin messages" to your users. You can prepare message and store them on the server, and your application can show them (whenever you want) to the user.

During the update process you can control wodAppUpdate's behavior. You can change file versions, their paths, you can force them (not) to be downloaded by setting NeedReplace property - etc.. You (or the user that uses your application) can cancel ongoing update anytime you want.

You can hide wodAppUpdate and silently perform the update, or you can use our own progress window and show it to end-user. wodAppUpdate will not initiate anything by itself, still you have full control, but it tries to make it as simple for you as possible, and yet very effective. You can also make your own dialogs since wodAppUpdate provides interface to integrate your application fully into the update process.

What's new in this version: 1.2.7 November 9, 2007 * UpdaterName is now checked upon startup. If there is another application running with same UpdaterName, your methods will fail (duplicate UdapterName causes problems between apps, since one app can try to update another)