With someone's help, I figured out the approach. After CostFinalize action, before InstallValidate action, add a customer action, say UpdateFeatureChange, which changes the feature's reqire state accordingly. In DTF, it is as simple as FeatureInfo featureA2= this.Session.Features["FeatureA2"]; featureA2.RequestState = InstallState.Absent; // Or Local/Source/Advertise... according to other conditions The DTF is using MsiSetFeatureState API to set the state. The condition is complex, because I need to handle different scenarios like repair/change/update/uninstall. However, this is a workable approach.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patching-and-Pyro-Warning-PYRO1110-tp7256794p7282912.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
