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

[Vanniekerk, Tyrel (GE Healthcare)]

So I assume the XML snippet bellow looks correct then?  At least at first glance.  Maybe a feature must have a least one component otherwise it does not get installed?

I will look into running the MSI directly. 

-----Original Message-----
From: Hoover, Jacob <Jacob.Hoover at greenheck.com> 
Sent: Monday, October 14, 2019 11:12 AM
To: Vanniekerk, Tyrel (GE Healthcare) <tyrel.vanniekerk at ge.com>; WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: EXT: RE: Convincing internal MSI to run during Modify mode with custom bootstrapper

Have you attempted to property drive the MSI from the command line to isolate if this is an MSI authoring error or a custom BA error?

-----Original Message-----
From: Vanniekerk, Tyrel (GE Healthcare) [mailto:tyrel.vanniekerk at ge.com] 
Sent: Monday, October 14, 2019 11:07 AM
To: Hoover, Jacob <Jacob.Hoover at greenheck.com>; WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: RE: Convincing internal MSI to run during Modify mode with custom bootstrapper

Yep, which means that my code bellow should work.  That's why I am confused.  I want it to install FeatureB if it's not installed and I am asking it to install.


>From that site:
For example, the conditional expression "&MyFeature=3" evaluates to True only if MyFeature is changing from its current state to the state of being installed on the local computer, INSTALLSTATE_LOCAL.

-----Original Message-----
From: Hoover, Jacob <Jacob.Hoover at greenheck.com>
Sent: Monday, October 14, 2019 10:23 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Vanniekerk, Tyrel (GE Healthcare) <tyrel.vanniekerk at ge.com>
Subject: EXT: RE: Convincing internal MSI to run during Modify mode with custom bootstrapper

https://docs.microsoft.com/en-us/windows/win32/msi/conditional-statement-syntax?redirectedfrom=MSDN



-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Vanniekerk, Tyrel (GE Healthcare) via wix-users
Sent: Monday, October 14, 2019 8:53 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Vanniekerk, Tyrel (GE Healthcare) <tyrel.vanniekerk at ge.com>
Subject: Re: [wix-users] Convincing internal MSI to run during Modify mode with custom bootstrapper

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>

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
NOTE: This email was received from an external source. Please use caution when opening links or attachments in the message.
NOTE: This email was received from an external source. Please use caution when opening links or attachments in the message.