Using: AD: 7.6.1:
Here's what happened:
1. I created a "main" msi, that has a couple of "Chained MSI's".
2. I choose to run the "Chained msi's" silently (no UI).
3. When I tried to install the "main" msi: it finished very quickly and didn't say that there was a problem.
4. I checked, and did NOT find that the "main" msi is installed in Add/Remove programs, I also did NOT find any of my chained msi's !!! So what really happened is: The "main" msi and all chained msi's did NOT install, but the Installer did NOT warn about this, and gave a "feeling" that everything is "okay".
So what I did is: I changed my "main" msi to run all chained msi's in "Full UI" (so that if any of the Chained msi's fails: I will see the problem), and then found the problem!
I had an error (Module xxxx failed to register...) - which is less interesting how to solve this, but more important is that I can choose between: "cancel", "retry" or "ignore", and I choose "cancel", but the installation of "main" msi doesn't say that the installation ended prematurely...
What I want is obvious: If even one of my chained msi's encounter some problem: then abort the installation of the "main" msi.
It looks like AdvancedInstaller should support this: but from my test I found that it doesn't... or am I missing something here?
Dashut.
FOLLOW US
Get the latest news in Application Packaging