I have two applications, "A" and "B". They are actually 99% the same assemblies, basically differing only in config files which dictate which classes obtain control (a very pluggable architecture). Thus we normally install all the assemblies, and pass the extra config file in the shortcut.
They want two installers: 1) One that installs "A" only (same files, one shortcut) 2) One that installs "A" and "B" (same files, two shortcuts) If a person installs #1, then #2, the result should be #2. They don't want two separate copies of the same application. Experimenting shows that if I create two MSIs, I get two separate copies. Is it practical to include two sets of dialogs in an installer, enabling "A and B" by defining a property at the command line? We'll have to launch the installer from a bootstrapper anyhow, and thought that perhaps I could give the same MSI two "faces" though a property. Or is there a better way to approach this that I'm not aware of? ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
