Our installer detects if our product or Outlook is running during install and uninstall. It works fine during install for the MSI and bootstrapper; during uninstall, however, it seems to only work from the MSI or from the add/remove program files (and the uninstall program control panel in Vista/7)--the process detection seems to not work at all for Outlook and seems to hang for detecting our own process. Is there anything special that needs to be done for process detection (and subsequently, terminating the uninstall) from the bootstrapper as opposed to the MSI?
Sorry for providing so little detail, but I've narrowed down and corrected the problem.
The issue was with the REMOVE property; for our error dialogs about our product or Outlook running, we had separate dialogs for uninstall. The launch expression for these was REMOVE="ALL". This was working using the MSI and has been our basic expression to check if the user was uninstalling. However, it appears that using the bootstrapper, REMOVE is a list of components being removed, rather than "ALL". I corrected this by instead using NOT REMOVE="".
Is there a reason the REMOVE property contains a list of components rather than "ALL" while using the bootstrapper? I don't believe we had this issue before, as this is a test case we run through each time we test our installer.
EDIT: Furthermore, it appears the MSI was working, as I mentioned above, only when run with msiexec from the command prompt. Apparently, REMOVE was showing the same behavior as in the bootstrapper when the MSI was double-clicked (i.e. our check for the processes was not fired off).
FOLLOW US
Get the latest news in Application Packaging