embedded msi
hi all,
i've embedded msi before, with CA 7 for install & CA 39 for uninstall. it's pretty neat.
but can i use this if i want my embedded msi to be installed first? where do i sequence my CA to make sure it is the first one to be installed?
thanks!
i've embedded msi before, with CA 7 for install & CA 39 for uninstall. it's pretty neat.
but can i use this if i want my embedded msi to be installed first? where do i sequence my CA to make sure it is the first one to be installed?
thanks!
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
- That depends on your definition of "installed".
- If the "host" MSI relies on the content of the nested MSI, you'll probably want to sequence it before the AppSearch and LaunchCondition CAs.
As ever with nested MSIs, you appreciate the problems you're going to have with patching/upgrading/updating the nested MSI? In general, it's agreed that this method is A Bad Idea.
- If the "host" MSI relies on the content of the nested MSI, you'll probably want to sequence it before the AppSearch and LaunchCondition CAs.
As ever with nested MSIs, you appreciate the problems you're going to have with patching/upgrading/updating the nested MSI? In general, it's agreed that this method is A Bad Idea.
Posted by:
kardock
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.