
I have a situation where we may have a third party .msi that needs to be fired as a child from our main install. The user would like the child .msi placed locally during the install in case they would need it for some sort of repair or reinstall.
That would be OK as I could simply fire the .msi from the target machine via custom action after it's installed. However, we need the child .msi to actually place its files before our main install because we move modify then replace some during our installation.
Can I fire the .msi from the Binary table during or at the tail end of the user interface (possibly as a control event), but also include the .msi as a component to be placed on the target machine?
Firing a child early on in the install has not caused me problems before, but I also need that .msi installed as well.
I don't know if there is a better way around my problem or not.
Any help is greatly appreciated!!