[wix-users] Getting around a 3rd party installer's reboot requirement

[Sean Krupa]

Thanks Jacob.  Adding the exit code behavior did solving the hanging issue.  The only other problem I'm having now is that the boostrapper reinitialises after rebooting and wants to run the 3rd party exe again.
--

Sean Krupa, Ph.D.

Optical Engineer

Sotera Defense Solutions, Inc.

o. 202-767-2193  c. 724-561-8932

e. sean.krupa at soteradefense.com

________________________________________
From: wix-users [wix-users-bounces at lists.wixtoolset.org] on behalf of Hoover, Jacob [Jacob.Hoover at greenheck.com]
Sent: Monday, April 24, 2017 10:46 AM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] Getting around a 3rd party installer's reboot  requirement

What is the exit code of the 3rd party installer when a reboot is requested?

It sounds like you need to add an ExitCode Behavior=forceReboot to your ExePackage element for the 3rd party installer which isn't using standard exit codes.

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Sean Krupa
Sent: Monday, April 24, 2017 9:21 AM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Getting around a 3rd party installer's reboot requirement

I'm using a bundle to manage a couple of my own installers plus a 3rd party installer.  The 3rd party requires a reboot to complete installation which is causing my bundle to hang indefinitely or fail if I exit the 3rd party installer.  Any thoughts on how to circumvent the reboot requirement?


--

Sean Krupa, Ph.D.

Optical Engineer

Sotera Defense Solutions, Inc.

o. 202-767-2193  c. 724-561-8932

e. sean.krupa at soteradefense.com<mailto:sean.krupa at soteradefense.com>

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/