One of the requirements for my installer is that it has to be possible to re-run the (same) installer after an initial install to recreate all the files (config files, executables). This also has to be doable without user interaction. The package has the Limit to Basic User Interface option checked. Upon install, the installed program is immediately launched.
If I simply re-run the foo.msi package a second time, the files are not replaced.
If I run a repair install using msiexec /fa foo.msi, then I get the pop-up "The following applications should be closed before continuing the install".
I tried adding a custom action to stop the installed program's process using the instructions here. The VBScript works correctly; if I run it by itself it stops the process. I have added the script as an Attached Custom Action to the FindRelatedProducts Standard Action.
Now, if I re-run the .msi package a second time, the files are not replaced, and the original installed program's process is not stopped.
If I run a repair install using msiexec /fa foo.msi, then I still get the pop-up "The following applications should be closed before continuing the install".
It does not appear that the VBScript is running.
FOLLOW US
Get the latest news in Application Packaging