Multiple updates for product at once

[georgem]

Is there a way to run through multiple updates in one go.
For example say we have product 1.0, 2.0 & 3.0.
Say each version upgrade requires different things to happen.
If a user has version 1 then we want the 2.0 logic to occur then it would detect we have 2.0 so do the 3.0 update logic, and so on.
TrueUpdate would handle this if you had the versions in ascending version order and it didn't stop when it found a match.
i.e. when it goes down the version list, if it finds a match then do the updates and then continue down the version list looking for a new match.
Can TrueUpdate handle this?
Regards

[Darryl]

TrueUpdate will only find one match and execute their actions, so it will not continue down the version identifier list to identify other versions.

What you will want to do is create version identifiers for each of your versions, each having the read value equaling each version, for example, version = 1.0, version = 2.0 etc.

For each of those versions you can launch whatever actions you wish. So in version 1.0's actions, you will want to add whatever actions are needed to bring them up to the newest version. The same would go for version 2.0. It's actions would be whatever is needed to bring the user up to the newest release.

Hope that helps. If you have any further questions, feel free to post back.

[georgem]

Darryl - thank you for the reply.
What you say is true but I am not sure it is that prectical.
Take the example we have version 1, then 2.0 comes out so we make that the latest version and put script in 1.0 to update to 2.0.
All fine, now some time later verison 3.0 comes out. We make that the latest version and make changes to 2.0 to upgrade it to 3.0.
What I would like to see is that this is all that needs to be done. If a version 1 user runs the process the 2.0 & 3.0 upgrades should be run consecutively.
Your suggestion would require me to also add the same upgrade logic to the 1.0 actions as well. This is fine until your list of versions gets up to say 20 or more, for each new version you will have to add its actions to all v - 1 versions before it.
Rather a lot of unecessary work and error prone as well.
Does this make sense?

[Darryl]

I certainly understand what you are saying and I will add your suggestion to be considered for a future version.

Being able to copy and paste actions, it may not be as bad as it appears, but yes, you would need to replicate that code.

Something you may want to consider for updating your software is a full history patching solution such as our Visual Patch product. so instead of creating a patch file that updates from only one version to the next, you would create one patch file that updates any previous version to the current version with a single patch executable.

This is the method we use for our products which results in only having two versions, one to detect they have the current version, and one to detect if they have any previous version. From your description, I don't know if this is a possibility, however I just thought I would mention it.