I have a .msi installer for a product that I'm distributing. During this installation, (it doesn't matter when), I would like to also install some VSTO add-ins.
Right now I'm calling the setup.exe files for the add-ins from an installer class in the Commit phase of my installation. However, this only works if the user already has the VSTO 3.0 run time files installed. The reason is that when the setup.exe is run, it detects that the VSTO 3.0 run time files need to be installed and attempts to install them, but fails when installing because "Another setup project is currently open".
I imagine this means I need to run the add-in setup.exe after my .msi has finished installing. But I'm not exactly sure how to do just that.
I briefly glanced at chaining but couldn't find anything that applied to my situation. I also considered trying to run the setup.exe from a vbscript custom action during the commit phase of the installtion, but I'm afriad this might give me the same result.
How can I go about running these setup.exe files after the .msi has completed installation, to prevent any errors with the installation of the VSTO 3.0 Runtime files?