[wix-devs] OnExecutePackageComplete without OnExecutePackageBegin
Rob Mensching
rob at firegiant.com
Thu Mar 17 10:35:15 PDT 2016
And in that unusual case, as Sean points out, to control it (if necessary) a bool is usually introduced.
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/
-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Bob Arnson
Sent: Thursday, March 17, 2016 10:33 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] OnExecutePackageComplete without OnExecutePackageBegin
All the Release* macros do that, just using NULL or some other value instead of an extra BOOL. If anything, the "do real work in LExit" is the unusual case.
> -----Original Message-----
> From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On
> Behalf Of Sean Hall
> Sent: Thursday, 17 March, 2016 13:28
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Subject: Re: [wix-devs] OnExecutePackageComplete without
> OnExecutePackageBegin
>
> I believe there is already precedence in burn to have a boolean
> initially set to false, then set to true once something happened. In
> LExit, it then performs additional work if it was set to true.
>
More information about the wix-devs
mailing list