On Fri, Oct 24, 2008 at 6:20 AM, Sébastien Mouren <[EMAIL PROTECTED]> wrote: > Yes, because instead of your CustomAction you already have a > StandardAction called LaunchConditions. It comes earlier in a "normal" > setup and you only have to put your <Condition /> action element here. > Your MSI must be heavier also but not by much. > > These are best practices.
Once you have more than a single Condition, you lose guaranteed control over which message is shown. You have no way of showing multiple or merged messages. Type 19 actions don't require any custom code, and are a fine practice when you need that additional control in order to avoid confusing your users. No bazookas here; perhaps hand drill vs. drill press? Now, if you implement a coded custom action, which sets a property to result in a Type 19 triggering, that could be a bazooka case. :) -- Michael Urman ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
