I currently have a .exe that loads a bunch of prerequisites (NET3.5, hotfixes, ...), including upgrades to Windows Installer (I need 3.1), and then finally launches my msi.
I would like to switch this to have a .msi that does everything and invokes an inline binary for each prereq. Hopefully this will be less error prone and I can better integrate the interface.
Before I begin to dive into this, does anyone know if this is possible and / or a good idea? I think run msi, and if the installer version is too low, update it and use customaction return = "asyncNoWait" to run the new installed version on the same msi.
I am new to installers, so any advice is welcome.
source share