Charlie Poole wrote: > My gui tests are a separate component under the tests feature. > Can I write a condition for that component that only installs > them if the gui feature has been selected? Is there a better > way to accomplish this? >
I don't think you can use feature conditions to do this, as in general, you'd run into circular conditions. In the past, I've handled this kind of thing with a custom feature-selection dialog. One "Documentation" checkbox used AddLocal and Remove control events to turn on/off subfeatures of each top-level feature. I was doing that intentionally to flatten the feature hierarchy. I also reasoned that there were three reasons people wanted to turn off features: - Disk space - Install time (directly related to disk space) - Intrusive system changes (e.g., services, drivers) Unless one or more of those reasons existed for a feature, it got flattened or hidden. Maybe that applies here? Another thing to consider is to make "base" a mandatory, hidden feature. That doesn't eliminate the problem entirely but it removes one level of hierarchy, so maybe that's enough. -- sig://boB http://bobs.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
