[wix-users] Convincing internal MSI to run during Modify mode with custom bootstrapper

[Vanniekerk, Tyrel (GE Healthcare)]

I have done a lot of reading and think I have a better grasp on how WiX/MSI process things.  I am still having an issue though, probably with my syntax.  Hope you can help.

In my bootstrapper log file it shows that the two features (One conditional, the other not) are planned to be installed (AddLocal).  In the MSI log file however it seems the condition on FeatureB was not evaluated as true, so that Request and Action is set to Null.  Seeing as I set the planned state for FeatureB to Local, who does (&FeatureB = 3) evaluate to false?

    [09A8:4B80][2019-10-14T08:23:45]i203: Planned feature: FeatureB, state: Absent, default requested: Unknown, ba requested: Local, execute action: AddLocal, rollback action: Remove
    [09A8:4B80][2019-10-14T08:23:45]i203: Planned feature: FeatureA, state: Absent, default requested: Unknown, ba requested: Local, execute action: AddLocal, rollback action: Remove

    MSI (s) (50:40) [08:23:59:166]: Feature: FeatureB; Installed: Absent;   Request: Null;   Action: Null
    MSI (s) (50:40) [08:23:59:166]: Feature: FeatureA; Installed: Absent;   Request: Local;   Action: Local


    <Feature Id="FeatureA" Title="Feature A" Level="1">
      <ComponentGroupRef Id="SomeId" />
    </Feature>
    <Feature Id="FeatureB" Title="Feature B" Level="0">
      <Condition Level="1"><![CDATA[(&FeatureB = 3)]]></Condition>
    </Feature>