Take a look at <Feature ... Absent="disallow" ... /> Absent attribute hides the feature as such from any display controls. Feature is still changeable through publish actions and/or conditions.
Original Message: ----------------- David Bartmess wrote: I have put conditions on the feature, but the problem is that the deciding variable is taken from input from a custom action that checks entitlements for each feature. This has to be done after the user enters a valid URL to login to (and possibly a username/password if the first attempt fails). This means that the variables that set features to be removed aren't set until the UI sequence, way after the CostFinalize phase, which is where I read > that the feature set is composed. If I could reset the feature set during the UI, that would be what I need... Rob Mensching wrote: > Not sure, but it sounds like you want to Condition the Feature. David Bartmess wrote: > I found that the Publish event AddLocal and Remove can set the feature to install or not to install, but it doesn't completely remove the feature from the list of features. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
