The action state of a featre is supposedly set after CostFinalize. Trying it out, it seems that checking the action state in the condition of a component, as you've done here, evaluates to -1, "unknown".
I would have thought that it would always evaluate to 3, "local", since the INSTALLLEVEL property has been set by then and CostFinalize has run in the UI phase (it runs before you see any dialogs). I would think it would always be 3 because that's the default. The changes the user makes in a UI feature tree wouldn't be evaluated, of course, until CostFinalize runs again in the execute phase. By experimentation, it looks like the feature's action state is -1 during the UI phase. Maybe &FeatureName only evaluates to anything else during the execute phase. In that case, you'd have to use a custom action to enable or disable components. Anyone know more about the -1 action state during the UI portion? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-with-feature-condition-not-actioned-tp5101940p5104423.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
