We have a MSI that has a custom MST. In this custom MST we call a EXT via custom action. Everything install fine. But, when we go into Add/remove programs and try to uninstall this package it fails.

What code do you put into your .MST to avoid this? I recall seeing some code by others that gets "wrapped" around the custom action.
0 Comments   [ - ] Hide Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity

Answers

0
add a condition to your custom action - NOT REMOVE~="ALL"
Answered 10/19/2009 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
where did you sequence the CA. is deferred or immediate etc
Answered 10/20/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment