Hello! My organization has started using Burn with a custom Bootstrapper Application to install multiple application "pieces" onto our servers. We currently use a dumbed down daily scheduling process inside of BladeLogic to install MSI's onto our servers and would like to start using this same process to run Burn executables on the servers. However, we're running into a roadblock because the compiled exe returns immediately even though the Burn engine and BA keep running. Our scheduling process was designed around the idea of waiting for an exe to return (and then evaluating return codes) before moving on to the next scheduled exe/MSI to run. This works fine when running msiexec.exe to install MSI's, but breaks down when running Burn exe's because they return immediately.
Is there some way that's not documented to make the exe wait until the Burn engine and BA are finished? I've scoured the Internet and haven't even seen anyone mention that this is an issue for them. My next move is to dig into the Burn source code. Based on my observations so far, it appears that the executable starts up the Burn engine and then returns immediately. The Burn engine then starts up the BA and works with it throughout the rest of the installation process. Any thoughts or knowledge about this would be helpful. Thanks! Anthony H ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
