You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use a pre-processor condition in the form of <?if $(var.A) ?>, the condition always evaluates to true regardless of the value of A. For example:
Should an atomic expression (with no value on the RHS of the expression) coerce the LHS value to a Boolean? In this situation could strings like '0', 'False', or 'No' be equivalent to Boolean False?
Relevant area of the WIX code base is EvaluateAtomicExpression() in src\tools\wix\Preprocessor.cs.
Unsure whether this is a bug, or a feature request.
Originally opened by rbradford
The text was updated successfully, but these errors were encountered:
Per triage team: We should not coerce to booleans. <?ifdef?> exists and comparisons to explicit values are supported. So a "naked" variable reference should be an error.
If you use a pre-processor condition in the form of
<?if $(var.A) ?>
, the condition always evaluates to true regardless of the value of A. For example:Should an atomic expression (with no value on the RHS of the expression) coerce the LHS value to a Boolean? In this situation could strings like '0', 'False', or 'No' be equivalent to Boolean False?
Relevant area of the WIX code base is EvaluateAtomicExpression() in src\tools\wix\Preprocessor.cs.
Unsure whether this is a bug, or a feature request.
The text was updated successfully, but these errors were encountered: