The Condition table is designed for enabling/disabling which features get installed at install-time. It sounds like your intent is to control which features get included into your various MSIs at build-time. For your situation the use of shared install code would enable you to have a similar setup as you did with Wise. I'd look into using fragments and/or wixlibs to organize your features, then just include them by reference into the various MSIs where they are needed.
There are several guides/blog entries on the web about how to use Fragments, wixlibs, ComponentGroups, FeatureGroups, etc. for organizing your WiX projects. I found them quite helpful when I was getting up to speed with WiX. Here is one example of a blog that illustrates how to organize your install using fragments. http://geekswithblogs.net/vagmi.mudumbai/archive/2004/11/23/15669.aspx The post is in the context of distributed development but fragments/wixlibs are equally good just for purposes of organization and code reuse. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Condition-Table-generation-tp5085798p5094460.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
