how to install multiple msi's at once
hi folks,
i have created an msi package that has 2 dependencies. 1 is another in msi i created that must be a separate msi and the second is msxml.msi
I see that i can use nested msi installs in installshield 2011 but i am wondering if this is the best practice?
I could also create a c# application that installs the 3 msi's but i feel like i am re-inventing the wheel if i do that.
can anyone let me know the best practices in this regard and let me know how to approach it?
thanks
i have created an msi package that has 2 dependencies. 1 is another in msi i created that must be a separate msi and the second is msxml.msi
I see that i can use nested msi installs in installshield 2011 but i am wondering if this is the best practice?
I could also create a c# application that installs the 3 msi's but i feel like i am re-inventing the wheel if i do that.
can anyone let me know the best practices in this regard and let me know how to approach it?
thanks
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
pjgeutjens
13 years ago
You might want to look into installing MSXML through a merge module in your main MSI
Posted by:
Teitan
13 years ago
There are some deployment systems which allow you to set dependencies on your packages so you could build chained installations.
Also you can deploy a VBScript which calls you installations in the right order.
Also you can deploy a VBScript which calls you installations in the right order.
Posted by:
anonymous_9363
13 years ago
I can use nested msi installs...a practice which is now strongly discouraged. Windows Installer 4.0 and above has the concept of "chained" MSIs but that obviously restricts you to that version and higher. All in all, I'd suggest using your deployment mechanism.
Posted by:
jmaclaurin
13 years ago
Its really up to you and how comfortable you are using the various technologies. There are also "best practices" and "not recommended" that you need to pay attention to as well. If this is an "in house" app, do what feels right and keep in mind that at some point, you may need to remove/upgrade this app. If this is something that will be available to the general public, please ALWAYS follow "best practices" and "not recommended" and save a lot of other people headaches.
Having said that, our company doesn't like chaining or nesting so we script everything in cmd files where we can. Otherwise, like already mentioned, we let our deployment tool handle the order of install.
Having said that, our company doesn't like chaining or nesting so we script everything in cmd files where we can. Otherwise, like already mentioned, we let our deployment tool handle the order of install.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
