Originally Posted by
markwa
As a SetupBuilder newbie but enthusiastic fan(!), I've successfully prepared a base setup for a 2.0.2 version of my app ("Composer"), and also a Web Update for version 2.0.3. My latest app version is 2.0.5. Users of version 2.0.2, 2.0.3, and 2.0.4 should all be albe to update in one step 2.0.5. I see evidence in this forum that this is possible, but I haven't been able to figure out how to do this.
The compiled 2.0.2-to-2.0.3 Web Update has three files:
(1) ComposerManifest.ini
(2) ComposerUpdate.00001
(3) ComposerUpdate.exe
If I create a second 2.0.3-to-2.0.4 Web Update, it also has three files like the above. I don't understand how these are essentially merged together in the 'update' directory at my server to support both 2.0.3-to-2.0.4 as well as 2.0.2-(to-2.0.3?)-to-2.0.4.
This raises a lot of questions:
* For each new version (eg, 205), do I need to prepare a new Web Update for each prior version: 202 to 205, 203 to 205, and 204 to 205?