Dear Advanced Installer team,
we just ran into another snag in preparing the installer for our product. Among the application itself, an Explorer namespace extension in a DLL gets installed. Deploying the product works fine, including some custom actions.
Problems arise when uninstalling or upgrading the product. The namespace extension DLL is still in use by the Windows Explorer, and cannot be uninstalled. In addition, a nasty "file is in use" dialog appears, which cannot shut down the Explorer. After browsing this forum, I've installed 2 custom actions taken from your RebootAfterUpgrade sample, and changed the conditions to REMOVE="ALL" AND NOT AFTERREBOOT. Uninstall gets correctly suspended, but no reboot takes place. After rebooting manually, an error message is displayed stating that the installer package cannot be found.
How can we achive the disred result of uninstalling/upgrading the product after a reboot, but before the Windows Explorer is launched? I've attached the .aip file along with the two VB scripts.
Thank you very much for your help,
Konstantin
P.S.: sorry for first posting under "Feature Requests"
FOLLOW US
Get the latest news in Application Packaging