Frank,

I am guessing here, the reason "NOT &Firebird=0" does not get evaluated to TRUE 
is because 0 is not a valid value for a feature state (see 
http://msdn.microsoft.com/en-us/library/aa368012(VS.85).aspx).

This description from Condition table 
(http://msdn.microsoft.com/en-us/library/aa368014(VS.85).aspx) has no direct 
relation to the feature state evaluation, but it shows that in certain 
situations Windows Installer evaluates invalid expressions to false:

"The expression in the Condition column should not contain reference to the 
installed state of any feature or component. ... Any expression in the 
Condition table that attempts to check the installed state of a feature or 
component always evaluates to false. "

Sorry, this is the only explanation I can come up with.

Alex





-----Original Message-----
From: Frank Cohen [mailto:frankensp...@gmail.com]
Sent: Wednesday, December 31, 2008 12:00 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Detecting if a feature is marked for install

Alex,

Thanks for your reply. This did the trick@  I don't completely understand
how it works, because shouldn't  "NOT &Firebird=0" and "&Firebird=3 OR
&Firebird=4" both evaluate to true if they're selected?  You make a good
point regarding the update and I've removed the "Installed" test.

Frank


------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to