[wix-users] How to make an execution order of a Custom Action configurable?
Blair Murri
osito at live.com
Fri Mar 1 16:55:08 PST 2019
To add it twice, you have to rename the copy
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: Charles Henze <Charles.Henze at dda.kyocera.com>
Sent: Friday, March 1, 2019 3:40:36 PM
To: WiX Toolset Users Mailing List
Cc: Blair Murri
Subject: RE: [wix-users] How to make an execution order of a Custom Action configurable?
Add the ExecuteSql once before, once after CreateFolder. Evaluate the condition on each based on which should run.
-----Original Message-----
From: wix-users <wix-users-bounces at lists.wixtoolset.org> On Behalf Of Blair Murri via wix-users
Sent: Friday, March 1, 2019 10:23
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Cc: Blair Murri <osito at live.com>
Subject: Re: [wix-users] How to make an execution order of a Custom Action configurable?
Can the order be easily determined by a condition expression? Or does it depend on something that won't be known until you start an installation transaction?
Get Outlook for Android<https://aka.ms/ghei36>
________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Wix Dev via wix-users <wix-users at lists.wixtoolset.org>
Sent: Friday, March 1, 2019 6:53:41 AM
To: wix-users at lists.wixtoolset.org
Cc: Wix Dev
Subject: [wix-users] How to make an execution order of a Custom Action configurable?
I am in progress with a custom WiX Toolset Extension and would like to know, if it is possible to make a custom action's order configurable?
For example, I have two actions:
1.
*CreateFolder* Custom Action:
<CustomAction Id="CreateFolder" BinaryKey="My.Ext.CA <http://my.ext.ca/>"
DllEntry="CreateFolder" Execute="deferred">
2.
*ExecuteSql* Custom Action:
<CustomAction Id="ExecuteSql" BinaryKey="My.Ext.CA <http://my.ext.ca/>"
DllEntry="ExecuteSql" Execute="deferred">
They are placed in the InstallExecuteSequence in the next order:
<InstallExecuteSequence>
<Custom Action="CreateFolder" After="InstallValidate">
NOT Installed
</Custom>
<Custom Action="ExecuteSql" Before="InstallFinalize">
NOT Installed
</Custom></InstallExecuteSequence>
It works fine for executing CreateFolder CA first, and then ExecuteSql.
But, in some cases it is required for WixExtension user to run ExecuteSql first, and CreateFolder comes next.
Can I somehow specify a CA order to be executed within InstallExecuteSequence and make it configurable?
____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users
mailing list