Burn doesn't do anything directly with Restart Manager today*. It will pass the "files in use" information that the Windows installer sends to the BootstrapperApplication. The BootstrapperApplication can respond as it wishes to the Windows installer. Really, you want your app to respond correctly to Restart Manager. Then everything will work very well.
* PS: Burn actually blocks Restart Manager from shutting the engine down while an install is going on. The BA will also get a callback when Restart Manager (or Windows directly) asks to shut the machine down. This improves the chances that the install is not unceremoniously killed while it is installing stuff. This behavior has nothing to do with your app shutdown/restart behavior. On Tue, Sep 11, 2012 at 1:34 PM, Wesley Manning <wmann...@dynagen.ca> wrote: > Hi, > > Have questions about restart manager in vista and above and how it works > with burn wixstaba. > > (1) Does burn use restart manager or something else to close open app when > it is left open on major upgrade? > > (2) I did a test where I have two versions of my burn installer, 1.4.2 and > 1.5.1. I install 1.4.2 and open the application (the main window of the > app opens) after install. I then leave the 1.4.2 app window open and > install 1.5.1 (normal install, not a quite/silent install). It seems that > burn does a forced shutdown of the 1.4.2 app and then installs the 1.5.1 > version of the app. Isn't it suppose display a dialog giving the user the > option of closing the app? Or is this considered a special case (as it's > the same application just a new version)? The only file being locked is > the old app's exe itself. > > (3) The problem I'm having is the I popup a message on shutdown if the > user has unsaved data. During the installation these notification popups > appear. It appears burn only waits for a finite period for the app to > shutdown and then continues to install regardless of if the old app > shutdown. Will listening to the WM_QUERYENDSESSION notification solve > this? If that notification is triggered by burn I can suppress the popups > on close. > > (4) Does this have anything to do with burn? I'm thinking maybe this is > MSI feature? Doesn't MSI 4.0 support the restart manager? > > I am planning on testing (3) sometime this week when I get a chance. > > Wes > > -----Original Message----- > From: Gregory Beaty [mailto:greg.bea...@gmail.com] > Sent: September-11-12 1:14 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Custom BootstrapperApplication installation > failure > > > > > > > Hello I have created a custom BootstrapperApplication based on the Wix > > 3.6 Installer. I am now up to point where I am ready to test actual > > installations. The log indicates that the log gets up to the point > > where it creates a system restore point then it does nothing. After > > closing the application several failures are written to the log. Note: > > When I use the standard BootstrapperApplication my application > > installs fine. Here is what I am seeing in the log file: > > > > [0A00:1A68][2012-09-10T20:13:23]: Burn v3.6.3303.0, Windows v6.2 > > (Build > > 9200: Service Pack 0), path: D:\installer.exe, cmdline: > > '-burn.unelevated BurnPipe.{890EC4BF-DB30-4EE2-88BB-10B738AB91B9} > > {255701DB-8529-4359-A8E5-5249C995A9A3} 7328' > > [0A00:1A68][2012-09-10T20:13:23]: Setting string variable 'WixBundleLog' > > to value 'C:\Users\Greg\AppData\Local\Temp\installer_20120910201323.log' > > [0A00:1A68][2012-09-10T20:13:23]: Setting string variable > > 'WixBundleOriginalSource' to value 'D:\installer..exe' > > [0A00:1A68][2012-09-10T20:13:23]: Setting string variable 'WixBundleName' > > to value 'Installer' > > [0A00:1A68][2012-09-10T20:13:23]: Loading managed bootstrapper > application. > > [0A00:1A68][2012-09-10T20:13:23]: Creating BA thread to run > asynchronously. > > [0A00:1A68][2012-09-10T20:13:24]: Detect 1 packages > > [0A00:1DF0][2012-09-10T20:13:24]: Creating the user interface. > > [0A00:1A68][2012-09-10T20:13:24]: Detected package: installer.msi, state: > > Absent, cached: None > > [0A00:1A68][2012-09-10T20:13:24]: Detect complete, result: 0x0 > > [0A00:1A68][2012-09-10T20:13:27]: Plan 1 packages, action: Install > > [0A00:1A68][2012-09-10T20:13:27]: Setting string variable > > 'WixBundleRollbackLog_installer.msi' to value > > 'C:\Users\Greg\AppData\Local\Temp\installer.msi_rollback.log' > > [0A00:1A68][2012-09-10T20:13:27]: Setting string variable > > 'WixBundleLog_installer.msi' to value > > 'C:\Users\Greg\AppData\Local\Temp\installer.msi.log' > > [0A00:1A68][2012-09-10T20:13:27]: Planned package: installer.msi, state: > > Absent, default requested: Present, ba requested: Present, execute: > > Install, rollback: Uninstall, cache: Yes, uncache: No, dependency: > > Register > > [0A00:1A68][2012-09-10T20:13:27]: Plan complete, result: 0x0 > > [0A00:1A68][2012-09-10T20:13:27]: Apply begin > > [1CA0:0DC4][2012-09-10T20:13:27]: Creating a system restore point. > > > > ====================================================================== > > =========== > > ====== > > Below only shows after I click the X button on the installer or the > > kill the process, which is an issue of its own. > > > > ====================================================================== > > ================== > > > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to write > > message type to pipe. > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to write > > send message to pipe. > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to send > > BURN_ELEVATION_MESSAGE_TYPE_DETECT_RELATED_BUNDLES message to > > per-machine process. > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to detect > > related bundles in elevated process > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to register > > bundle. > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to write > > message type to pipe. > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to write > > send message to pipe. > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to send > > message to per-machine process. > > [0A00:1A68][2012-09-10T20:13:59]: Apply complete, result: 0x800700e8, > > restart: None, ba requested restart: No > > [0A00:1A68][2012-09-10T20:13:59]: Shutting down, exit code: 0x0 > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleAction = 4 > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleElevated = 1 > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleLog = > > C:\Users\Greg\AppData\Local\Temp\installer_20120910201323.log > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleLog_installer.msi > > = C:\Users\Greg\AppData\Local\Temp\installer.msi.log > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleName = Installer > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleOriginalSource = > > D:\installer.exe > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleProviderKey = > > {a978a4e0-4cc1-4c9a-bd00-1e9dac268a9f} > > [0A00:1A68][2012-09-10T20:13:59]: Variable: > > WixBundleRollbackLog_installer.msi = > > C:\Users\Greg\AppData\Local\Temp\installer.msi_rollback.log > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleTag = > > [0A00:1A68][2012-09-10T20:13:59]: Variable: WixBundleVersion = > > 2.5.4592.29737 > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to write > > message type to pipe. > > [0A00:1A68][2012-09-10T20:13:59]: Error 0x800700e8: Failed to post > > terminate message to child process cache thread. > > [0A00:1A68][2012-09-10T20:13:59]: Exit code: 0x0, restarting: No > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and threat > landscape has changed and how IT managers can respond. Discussions will > include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
