Brian, Thanks, I was thinking something along these lines for the future. At the moment a simpler request, perhaps. How can I chain two installations? For example, most of the time I ship my app and a database. If the installers are separate, I would like to install the app first, then the database. Of course, I also need .Net, and hence am using the bootstrapper in VS via Wix.... which is perhaps an added complication. Any suggestions? This would be a step in the right direction for the full modular system.
Cheers, Nick -----Original Message----- From: Brian Rogers [mailto:rogers.br...@gmail.com] Sent: 30 September 2009 18:32 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Modular install configurations based on availablefiles Hey Nick, I would look at Burn to help you accomplish some of your goals. You could make an individual MSI for each database you are shipping. Compile those individual MSIs into Burn and then use the search features of Burn to determine which databases have already been installed via MSI searches and choose which to install later. Each MSI would have business logic for how to install the database. This would help you keep things modular in the long run. It would also help you with patching and upgrade support. Databases are, IMHO, one of the hardest installs to upgrade through MSI (good luck). The cab file approach wouldn't be an MSI/WiX approach in the long run. Hope that helps, Brian Rogers "Intelligence removes complexity." - Me http://blogs.msdn.com/icumove <-- NEW On Wed, Sep 30, 2009 at 9:00 AM, Nick Ball <nick.b...@grantadesign.com>wrote: > Hi All, > > > > I have a product that ships with several different databases - or > combinations thereof. I would like my installer to show all available > databases as features that the user can install - and those that didn't > get shipped should be greyed out. > > > > I'm thinking of one main setup program and each database stored as a > feature in separate cab files. I can either then look on the source disk > for each cab file in turn, or write a small XML file (like office seems > to do) describing the components and where they are. At the moment, I'd > like to do everything in WiX. > > > > A couple of questions. > > > > 1. Is it easy to look for named cab files? If so how? What are the > problems with this approach (I'm thinking that a repair would need the > source disk for this to work). > > 2. If the config was stored in an XML file instead of searching > for CABS, how would this get round the repair problem? > > > > Any other suggestions that would help me create a modular installation > welcome. > > > > Regards > > > > Nick > > > > > ------------------------------------------------------------------------ ------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
