A few questions have been asked regarding this example and I would like to point out some things to help clear up a few misunderstandings.

With every update that you build with AppLife Update, you can define exactly which previous versions of your application can apply this update.  Some applications make every update package available to all previoius versions.  In this case, there would never be a need for chaining updates.

And some applications make breaks in the availablity with releases that include new support information such as help files and examples.  Breaks like this are usually done to decrease the update package file size.  For an update to be available for all versions or a range of versions, it must include everything that the lowest version that can apply the update package needs.  So usually, the decision to make an update available for only specific versions is based on file size and what can be excluded for newer versions.  For applications that update often and are published for only specific versions, this example presents a means to chain the updates together in a single unified process so that a new user installing your application from dated media, or infrequent application users can get all the updates in one process.