12/07/2009 2640 views

I am upgrading 3 versions , lets say a,b,c while installing the product "D" . Is there any way that msi "D" can cotrol the installation sequence of upgardes a, b, c.
What i meant is application should upgrade "c 1st" and then "b next" and then "c".
by default it is uninstalling "a , b then c".
please send the response.

0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

I can't think of any way that you could control the order but then neither can I think of a reason why one would need to. If a component needs to be upgraded, it'll be upgraded: why does the order matter?
Answered 12/07/2009 by: VBScab
Red Belt

Hi ,

Thanks for your quick response.

Vendor has created three msi's and included some customactions and those are already there in live environment.They gave some sequence to uninstall , other wise it will throw some errors becuase of vb script customactions.Thats the reason we need to upgrade in that sequence only.
Answered 12/07/2009 by: joseph
Orange Belt

you might have to script the uninstalls outside your actual MSI.
As in a VBS or something calling sequential MSIEXEC /x 's

Also, call the vendor and yell at them.

Answered 12/07/2009 by: pjgeutjens
Red Belt

You need to be careful with your terminology, since a Windows Installer "upgrade" covers a scenario where an MSI will perform (what I call) an "in-place" upgrade, i.e. the package contains all the information it needs to upgrade all the components of a version (or several versions) of a product.

As Pieter points out, you're probably going to have to script the uninstallation sequence. Use some intelligent script, like VBS, so that you determine the success of a step before you progress to the next one.
Answered 12/07/2009 by: VBScab
Red Belt

ask VF to go to hell.
Answered 12/08/2009 by: mekaywe
Brown Belt