What is the prefered method of installing msi which are getting installed one after other ?

Thanks a lot in advance
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I'd personally avoid using nested MSI's if at all possible. There are plenty of notes in this forum and elsewhere that explain some of the pitfalls, but to start you off ...

(i) lack of add/remove programs entry for the nested application - you need to uninstall the "parent" as well to uninstall the nested one.

(ii) poor rollback support - there is no easy way to set up a rollback to uninstall the nested package.

The title of your note suggests that the proposed nested msi has a transform. I may be wrong on this, but I think you might need to merge this transform with it's base MSI before using the resulting transformed MSI as a nested package. I'm not sure there is provision for transforms when using Custom Action type 7, which is what a nested MSI installation is.

A lot depends on your deployment method, but I'd go for a batch solution calling the first MSI, followed by the second. You could set up a System Search in the second package that checks that the first one was correctly installed before it is allowed to proceed.


Answered 07/21/2006 by: spartacus
Black Belt

Please log in to comment