[wix-users] Convincing internal MSI to run during Modify mode with custom bootstrapper
Vanniekerk, Tyrel (GE Healthcare)
tyrel.vanniekerk at ge.com
Fri Oct 11 09:08:09 PDT 2019
I think I am narrowing in on an answer for this. The standard blog about creating a custom bootstrapper installer actually has some extra information I had not noticed before, so I am reading through it again from the start.
So far I know that I was missing the attribute to enable feature detection (EnableFeatureSelection="yes") and I was missing the OnPlanMsiFeature event.
I will get there in the end. 😊
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Vanniekerk, Tyrel (GE Healthcare) via wix-users
Sent: Thursday, October 10, 2019 2:44 PM
To: wix-users at lists.wixtoolset.org
Cc: Vanniekerk, Tyrel (GE Healthcare) <tyrel.vanniekerk at ge.com>
Subject: EXT: [wix-users] Convincing internal MSI to run during Modify mode with custom bootstrapper
I am trying to get modify mode working correctly for my installers. From my understanding, if no features have changed, the package will be detected as present and the bootstrapper won't even call the MSI. So logically, if you have a feature in the MSI that you change from installed to not or vice versa, the bootstrapper will run the MSI to perform that action.
I added an event handler for DetectMsiFeature and I get the current value of the feature. Then I set a variable to the opposite value. Problem is that it does not change that I want the state to be Absent.
I added a feature to my internal MSI per the WiX web site and I changed the value of ENABLE_FEATURE_CHANGE to be the opposite value from what it currently is.
<Feature Id="FeatureChange" Title="Feature To Force Change Mode" Level="0">
How can I convince the bootstrapper to run my internal MSI to make the feature change?
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users