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
