This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Unlocking files or folders
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jun 22, 2010
01:28 PM
Unlocking files or folders
I have a service that when run it locks a folder from being deleted. This is obviously a problem when uninstalling.
Is there a property I can set to force InstallShield to delete a folder that is locked? Or force it to unlock a folder? The folder in question is in my project path.
By the way, stopping the service and even uninstalling it does not unlock the folder.
Thank you.
Is there a property I can set to force InstallShield to delete a folder that is locked? Or force it to unlock a folder? The folder in question is in my project path.
By the way, stopping the service and even uninstalling it does not unlock the folder.
Thank you.
(2) Replies
‎Jun 22, 2010
06:26 PM
Strange that shutting down the service keeps the directory locked; if you use Process Explorer or similar tool, is there an indication of what's holding on to the directory? There are APIs for stopping processes or rebooting the system after uninstallation, but ideally if there's a root cause to remove...
‎Jun 23, 2010
08:18 AM
We got same kind of issue (lock folders after uninstalling only on Windows 7)
it was related here some time ago http://community.flexerasoftware.com/showthread.php?t=190916
After some investigation we discovered it was because COM extract at build option was not working fine with a mixed (dual) COM/.NET dll.
We removed COM extract at build option and set registrey keys "manually" for COM and issue was fixed .
Bernard.
it was related here some time ago http://community.flexerasoftware.com/showthread.php?t=190916
After some investigation we discovered it was because COM extract at build option was not working fine with a mixed (dual) COM/.NET dll.
We removed COM extract at build option and set registrey keys "manually" for COM and issue was fixed .
Bernard.