When a msi is run in upgrade mode how do you determine/control what
customActions do not run during upgrade processing? I have a v1.0 msi that
I'm now creating a v1.0 sp1 version of and associated patch msi. If I run the
v1.0 sp1 msi in upgrade mode on an existing v1.0 install I have a bunch of
customActions I want to not run since my 1.0 to 1.0 sp1 release differences
only involves binary file updates.
-------------------------------------------------------------------------
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
