[wix-users] Question about commit custom actions

Paul Mumford paul.mumford at gmail.com
Fri Dec 8 14:58:34 PST 2017


Yeah take a look at the event sequence in the actual MSI Microsoft
documentation. Its counter intuitive when compared to how things go in
order in the WiX XML but its all there somewhere.

Start point https://msdn.microsoft.com/en-us/library/aa371621(v=vs.85).aspx

On 8 December 2017 at 22:32, Edwin Castro via wix-users <
wix-users at lists.wixtoolset.org> wrote:

> I don't know the real answer here but I'm going to make an educated guess.
>
> I guess that commit actions are executed at the end of the install
> transaction. If this is the case, then that might explain why the 1.0.
> commit action doesn't run until 2.0 finishes since the install transaction
> closes/ends after 2.0 completes InstallFinalize.
>
> --
> Edwin G. Castro
>
>
> On Fri, Dec 8, 2017 at 2:06 PM, Joel Budreau via wix-users <
> wix-users at lists.wixtoolset.org> wrote:
>
> > I honestly can't seem figure this out from the log files :(
> >
> > Here's my situation:
> > - I'm performing a major upgrade from msi 1.0 -> msi 2.0
> > - 2.0 has RemoveExistingProducts immediately after InstallInitialize
> > - 1.0 has a commit custom action that executes during an uninstall (by
> > accident)
> >
> > It appears that the 1.0 commit action is getting executed at the end of
> the
> > 2.0 install, not at the end of the 1.0 uninstall. Is this expected? Would
> > the 1.0 commit action get scheduled in such a way that it doesn't execute
> > until after the 2.0 finishes InstallFinalize?
> >
> > Thanks,
> > Joel
> >
> > ____________________________________________________________________
> > 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