Add/Remove Applet's Remove Button
I have noticed that when the user clicks Remove from the Add/Remove Applet, it bypasses the UI Maintenance dialogs, while this does not really matter to me, what I do care about is that when I click Remove my CustomAction does not fire, which I assume is because it is in the UI sequence, so if i place the CA in the execute sequence will it still get fired when the user clicks the remove button?
ps i am testing this too, but I would stil appreciate some good info on the Remove vs Change button functionality!
ps2 is there a way I can set the Remove button to run the full maintenance/ui sequence?
That's correct: the user's clicking Remove runs the command msiexec /x [ProductCode], which skips the UI sequence; I'm not aware of a way to change that.
You can place a custom action in both the UI and Execute sequences, if you need it always to run...
thanks robert, a fellow InstallShield Developer here in my office, said he thought in I.S. Professional there was a way to accomplish changing the remove buttons functionality? Just curious though, why would script/procedural setups have that capability, and msi/database setups would not?
I just placed the CA in the execute sequence using Installed condition, and it is executing regardless of which commandline parameter is used with msiexec.
For pure MSI setups, the OS handles the behavior of the Change and Remove buttons; for non-MSI setups (including Developer 7 InstallScript-based projects), there's only that single Change/Remove button, which launches the command listed in your product's Uninstall registry key...