For your second question:
you need to surround that statement with
so that the XML parser does not
interpret "<>" as an empty element. Alternatively, you can use
CONDITION_PROPERTY < > "F1"
> installed! Why?
>
> And another question...
> I tried to use '<>' as 'not equal' comparative opera
I believe that this is expected behavior for MSI. Conditional features are evaluated during the CostFinalize standard action, which must be executed BEFORE the UI is displayed. This allows for conditional feature installation based on properties that are setup prior to the UI running - such as OS
I'm trying to install feature depending on condition. I wrote following
code:
NOT (CONDITION_PROPERTY="F1")
NOT (CONDITION_PROPERTY="F2")
During installation I have a dialog that sets CONDITION_PROPERTY with
one of the available value (
3 matches
Mail list logo
