On 08-Jan-13 10:54, John Cooper wrote: > Conceptually, it requires carefully embedding debug code in your working > immediate custom actions that is triggered only when the mutating variable is > set to certain values. The part about embedding debugging code into my > custom actions is a little scary. But having an immediate custom action > complex enough to require several different run scenarios is also scary. It's normal for a scheduling CA to run for scenarios like install, upgrade, uninstall, etc. That's probably the primary use case for mutations. The idea is that you have a variable of type WCA_TODO that's set normally, then overridden in an #ifdef DEBUG block to whatever the mutation is.
The secondary use case is to allow you to inject faults so you can test your error handling. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
