The hackery required to survive reboot makes this sure to not work. So from the matrix of advantages: Transparency: No. NET 4 requiring a reboot sometimes) we have to do further hackery. Theoretically possible but since a reboot may be required (thanks MS for. Missing piece: attended/unattended does not seem to be available.Īnyway, the only to make this work at all would be for the custom action to kill its parent process!ĮDIT: So somebody posted as a further answer wrapping the whole thing as a post-install custom action. If it works, I'll be accepting it.ĮDIT: it does not work. I just haven't had a chance to try it yet (crunch time). Options to an MSI are explained in Msiexec (command-line options) (low level "run" of an MSI is msiexec option package.msi).ĮDIT: mjmarsh's WiX solution looks like it works. So, how can I create an MSI file that extracts an EXE file to a temporary directory and runs it with options same or similar as were passed to the EXE file? After way too many experiments, I've come to the conclusion that Windows Installer is simply bad technology.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |