I've currently got an .exe that bootstraps a bunch of prerequisites (NET3.5, hotfixes, ...), including upgrades to Windows Installer (I need 3.1), and then finally runs my msi.
I'd like switch this to have an .msi that does everything, and calls an embedded binary for each prereq. Hopefully this'll be less error-prone plus I can integrate the UI better.
Before I go sinking time into this, does anyone know if it's possible and/or a good idea? I'm thinking start the msi, and if the installer version is too low then upgrade it and use a customaction return="asyncNoWait" to run the newly installed version on the same msi.
I'm new to installers, so any advice is appreciated.