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
- :
- Deleting INSTALLDIR on uninstall even though it is not empty
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 08, 2009
08:39 AM
Deleting INSTALLDIR on uninstall even though it is not empty
Hi,
I want to delete INSTALLDIR on uninstall. It is not deleted automatically, since the product writes log files in that directory, so the directory is not empty after the uninstallation had deleted all the product's files.
I believe that the way to do this is with Custom Actions. If I'm wrong, I'd be happy if someone explains to me how to do this. If I'm right then I cannot use VBScript because I cannot pass arguments to scripts (again, if I'm wrong, please explain how I pass arguments to scripts). So, it looks like I must write an EXE and call it from Custom Action, because it's the only way, right?
Thanks.
I want to delete INSTALLDIR on uninstall. It is not deleted automatically, since the product writes log files in that directory, so the directory is not empty after the uninstallation had deleted all the product's files.
I believe that the way to do this is with Custom Actions. If I'm wrong, I'd be happy if someone explains to me how to do this. If I'm right then I cannot use VBScript because I cannot pass arguments to scripts (again, if I'm wrong, please explain how I pass arguments to scripts). So, it looks like I must write an EXE and call it from Custom Action, because it's the only way, right?
Thanks.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 08, 2009
10:32 AM
Actually, no. Even though you can't pass parameters to a VBScript custom action, you could set things up so that the VBScript could have access to MSI properties which is what you would need.
But an even better approach is to avoid the custom action route completely, in this case, and make use of the RemoveFile table. In that table you can specify additional files to be removed on installation or uninstallation of a component.
But an even better approach is to avoid the custom action route completely, in this case, and make use of the RemoveFile table. In that table you can specify additional files to be removed on installation or uninstallation of a component.
