I have an aip file, using the simple UI. After some recent changes (adding some more binaries, and a file removal), the simple UI has started prompting the user to close applications prior to running the install.
I can't see what changes would have triggered this. Can you tell me what makes the UI ask the user to close applications prior to continuing? Is there any way to prevent this behaviour - i.e. force the install to proceed without asking the user to close running apps?
Thanks in advance,
David.
Suggested Articles
Hi David,
This in not related to the installation package running with simple UI or not.
This behavior is caused by the fact that Windows Installer cannot overwrite an application that is running. So, if your package is installing an application over the previous version, and the older one is still running this message will appear.
I am afraid that you cannot prevent this behavior, since this is the way Windows Installer works.
Hope this helps.
Regards,
Mihai
This in not related to the installation package running with simple UI or not.
This behavior is caused by the fact that Windows Installer cannot overwrite an application that is running. So, if your package is installing an application over the previous version, and the older one is still running this message will appear.
I am afraid that you cannot prevent this behavior, since this is the way Windows Installer works.
Hope this helps.
Regards,
Mihai
Mihai,
Thanks for your help - that does clarify things.
The case I have is slightly different, but I imagine the reason we are asked to close an app is similar to the case you outline.
Our install is triggered by the Found New Hardware wizard, via a co-installer. Our app is not running when we install. However, we do have a File Removal item in our msi to delete the co-installer used by the Found New Hardware wizard.
This File Removal item is only run on component uninstall, but I imagine the installer takes note that the co-installer is in use, and is also referenced in the msi, and requests we close the application that is using it (i.e. the Found New Hardware wizard).
I'll find another way to remove the co-installer.
Thanks,
David.
Thanks for your help - that does clarify things.
The case I have is slightly different, but I imagine the reason we are asked to close an app is similar to the case you outline.
Our install is triggered by the Found New Hardware wizard, via a co-installer. Our app is not running when we install. However, we do have a File Removal item in our msi to delete the co-installer used by the Found New Hardware wizard.
This File Removal item is only run on component uninstall, but I imagine the installer takes note that the co-installer is in use, and is also referenced in the msi, and requests we close the application that is using it (i.e. the Found New Hardware wizard).
I'll find another way to remove the co-installer.
Thanks,
David.