1. If there are accessibility bugs in the wixstdba, we should work to fix them. Please, feel free to file them. Sounds like you'd recognize them quickly. <smile/>
2. Popping up multiple-MSI UI's is definitely not the easiest. I mean, we could do it in Burn but it would not work well. You'd still need something during the detection/planning/caching phases. It sounds like you really want the old WiX v3.0 "chainer" that just launched one MSI after another (it was really weak <smile/>). 3. The wixstdba doesn't currently do any feature selection. I'm toying with some ways to map "features" to check boxes. Now, you can set conditions on features in an MSI package and I'm pretty close to arbitrary mapping of checkboxes to Burn Variables so that gets closer. Anyway, there is more to do in the WiX standard bootstrapper application but you can always write your own to customize things far more than the standard bootstrapper application. 4. I want to reiterate that last point. Burn is designed to enable you to write your own bootstrapper application. You can do so in native code or managed code. If you want to do something special you can without having to do tons of the hard stuff like download resume, interpreting MSI progress and multiple package rollback. On Tue, Jan 4, 2011 at 12:25 PM, Sean Farrow <sean.far...@seanfarrow.co.uk>wrote: > Hi: > Interesting points, but given that the current ui has issues in the core > market this project is working in, (accessibility) this seemed like the > obvious or at least the quickest solution! > How does the current burn ui handle multiple features are they selectable, > or does it just install everything? > Cheers > Sean. > > -----Original Message----- > From: Christopher Painter [mailto:chr...@deploymentengineering.com] > Sent: 04 January 2011 17:35 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Burn issue > > > Rob, > > That's an interesting comment but it makes me think of the Visual Studio > experience. It's a seamless experience installing a bunch of packages but > the result is the same. You pretty much have to reformat to get back to the > original state. Either that or run through lengthy complicated procedures > to get it all off. > > Now with Visual Studio that normally isn't such a bad thing since > generally everything it installs are things that I actually want where as > with products like iTunes ( and others ) many of the things are not always > things that I actually want. > > So back to burn... how does it manage the uninstall experience? If Visual > Studio was done with Burn, would it have a "take it all off" experience? > > Chris > > Christopher Painter, Author of Deployment Engineering Blog > Have a hot tip, know a secret or read a really good thread that deserves > attention? E-Mail Me > > > --- On Tue, 1/4/11, Rob Mensching <r...@robmensching.com> wrote: > > > From: Rob Mensching <r...@robmensching.com> > > Subject: Re: [WiX-users] Burn issue > > To: "General discussion for Windows Installer XML toolset." < > wix-users@lists.sourceforge.net> > > Date: Tuesday, January 4, 2011, 10:39 AM > > 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. > > > > Many years ago my wife got an iPod shuffle as a present. To > > use it we had to > > install iTunes. The install was such a mishmash of > > disparate installation > > packages that by the time it was done I was sure the only > > way to get the > > machine back to normal would be to format it. Burn is > > designed to provide > > the antithesis of that experience. <smile/> > > > > -- > > virtually, Rob Mensching - http://RobMensching.com LLC > > > > On Mon, Jan 3, 2011 at 10:22 AM, Sean Farrow > > <sean.far...@seanfarrow.co.uk>wrote: > > > > > Could this be added? > > > Cheers > > > Sean. > > > > > > -----Original Message----- > > > From: Rob Mensching [mailto:r...@robmensching.com] > > > Sent: 03 January 2011 16:29 > > > To: General discussion for Windows Installer XML > > toolset. > > > Subject: Re: [WiX-users] Burn issue > > > > > > No. Burn doesn't show the UI from the MSIs. > > > > > > On Sun, Jan 2, 2011 at 3:28 AM, Sean Farrow < > sean.far...@seanfarrow.co.uk > > > >wrote: > > > > > > > Hi: > > > > I'm using Burn as a container to hold two msi's. > > > > I'd like to use the ui's from the msi in the > > current implementation. > > > > If I remove the bootstrapApplicationRef element I > > get a lght0001: the > > > > given key is not in the dictionary. > > > > Is there anyway to use the ui from the original > > msi? > > > > Any help appreciated. > > > > Sean. > > > ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
