Following on my experience with AppLife Update...



One of my project is currently being beta test by one customer on 3 workstations, the method I was using to release beta updates was:

1.- Build my beta release in VS

2.- Building another InstallAware setup (with all files) or creating a zip file with just the files that have changed.

3.- Upload my update to my FTP server.

4.- Remote login to those 3 workstations

5.- Download update to a share folder

6.- Apply and test the update on each workstation, not to mention that one of those workstations have a very tight security, so I had to run my update programs with the "Run As" option, otherwise the update will not install or ask the administrator to do it himself which he will not be happy to do.



Now with AppLife Update, the whole process was completely simplified:

1.- Build my beta release in VS

2.- Create an update with AppLife Update which will compare new version with previous one and just build the files needed for the update and will also automatically upload the update to my FTP server.

3.- Customer press a button on my application to "Check for updates" and accept the update. AppLive update will close my application, apply the update, then opens up my application when update finished.



I just did a quick build today to fix a bug and in less than 10 minutes customer was up and running the new version.



I have to be honest, I am using the simplest way to apply update using the UpdateInterative method, so when I start digging the custom updates with all events available on my main form, then that will be another chat

Edhy Rijo