The problem is that it does not wait for the application to terminate, which often leads to a "file in use" condition.
One common sequence of immediate custom actions that I added in our installers is the following:
- Close application
- Detect process
- Bail out of installation process if process detected
With the default custom action "Close application", the installation process is also stopped prematurely in cases where the application could actually be successfully terminated in the current user session.
Therefore, to make the default custom action "Close application" more useful, it should wait a specified time for the process handle to be signaled.
FOLLOW US
Get the latest news in Application Packaging