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
- :
- Conditionally uninstallation of application and user data
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
‎Oct 27, 2008
04:26 AM
Conditionally uninstallation of application and user data
hi,
our application creates some user setting files and database files.
These files should be removed conditionally (checkbox on ReadyToRemove dialog).
Question 1:
Can these files and folders being removed using MSI tables or do they have to be removed inside a custom action?
Question 2:
Installation is a per-machine installation but user settings will be stored for each user by the application. Can these be uninstalled for all users or only for the current user?
-Holger
our application creates some user setting files and database files.
These files should be removed conditionally (checkbox on ReadyToRemove dialog).
Question 1:
Can these files and folders being removed using MSI tables or do they have to be removed inside a custom action?
Question 2:
Installation is a per-machine installation but user settings will be stored for each user by the application. Can these be uninstalled for all users or only for the current user?
-Holger
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 30, 2008
06:25 AM
anyone please?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 30, 2008
10:24 AM
The only built-in option for 1 is the RemoveFile table, which can remove associated files when a component is installed or uninstalled. At uninstall, this can only be an component uninstall, and unfortunately there is no way to condition that. You might be able to fake out conditioning by creating an extra Directory entry and carefully setting it to something unusable, but I don't think I'd recommend that sort of trick, even if it works. So yeah, go custom action.
For 2, built-in will only handle the current user, and that only if it's resources installed by the .msi tables. If this configuration is supplied by the application when it runs, etc., there's nothing built-in for the uninstall. In general it is recommended that configuration be left behind so user B doesn't lose settings when user A uninstalls and reinstalls a per-machine installation.
For 2, built-in will only handle the current user, and that only if it's resources installed by the .msi tables. If this configuration is supplied by the application when it runs, etc., there's nothing built-in for the uninstall. In general it is recommended that configuration be left behind so user B doesn't lose settings when user A uninstalls and reinstalls a per-machine installation.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)