We Installed a msi using the "new nested msi" custom action in installshield 2009. It installed successfully, but unable:mad: to uninstall the nested msi from the system. Please help us to stay away from this.
Nested (or concurrent) installations are deprecated, nowadays, in favor of chained installations, InstallShield prerequisites, and almost anything else, so if there's another approach you can use...
(Back when they were used, one would uninstall the nested installation with a second "nested installation + already on the system" action, setting REMOVE=ALL with the action and using action condition REMOVE="ALL", but if you can possibly avoid it...)
