#1 and #2: If SQL Express installer would come as .MSI then upgrade detection would be simpler. I was not able to find .MSI, only .EXE. This makes upgrade detection more difficult. But, if you have your own managed bootstrapper, you can do whatever you want. You should be able to detect existing SQL express installation (using registry or some other method) before you let Burn to do detection and then you can ask user for upgrade permission and set appropriate action for your bundled SQL express installer (to not install it if user does not want upgrade). #3: If you have own managed bootstrapper, you can run installer that user provides as a new process using Process.Start(). You won't get direct integration with your installation so you will have to handle that somehow (showing progress etc.) but you should be able to wait for SQL server installer to finish and then continue with your installation. But this way you won't get rollback for SQL server in case your install fails etc.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Prerequisite-Install-and-Configuration-tp7600137p7600144.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
