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
[ - ] Hide Comments

so that the conversation will remain readable.
Answer this question
or Comment on this question for clarity
Answers
- 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.
Please log in to comment
Comments