Ultimately I am controlling what the user sees, the stripping out of the merge modules is simply reducing the size of the package. Using the condition table I have a consistent feature table for all packages, and encapsulate exclusions within each package.
Probably FeatureGroups will work, but at the expense of decomposing the feature tree to isolate pieces that are now or may later be excluded. Instead of having a consistent feature table which I can make into a wixlib, I need to create a series of FeatureGroups and build the tree in each project. More work, less encapsulation, more duplication. Enhancing Wix with the ability to specify a Condition as a child of the FeatureRef would allow the feature tree to remain intact, with FeatureRef entries describing the condition table in each <Product />. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Condition-Table-generation-tp5085798p5095129.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
