Rob Mensching <rob <at> robmensching.com> writes: > Maybe. It's not really in the model Burn was designed for. Burn was intended > to provide a seamless installation experience not pop up a bunch of > different installation wizards. [skipped] > Burn is designed to provide > the antithesis of that experience. <smile/>
What if someone still wants to install main msi-package (using the package UI) and deploy it's dependencies in a silent mode? The dependencies are a subject to remain on user machine (almost always) permanently (Windows Installer redist, Visual Studio redist etc.) I'd like to use UI from the main package, which I have to create anyway. Another scenario, when I need to install a single msi-package conditionally from a single multi-package installer. In that case I'd prefer to use UI of embedded msi-package, rather than create new UI for bootstrapper. Unfortunately the old bootstrapper from WiX 3.5 doesn't support chain conditions, but Burn doesn't show UI of embedded packages. Am I forced to write my own bootstrapper or extension to Burn in that case? -- Vitalii Dolia ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
