I have an existing product that I need to break out into a few individual products due to the large size.
As such, I would like to have: Core.msi - The core product needed by other products Add_On1 Add_On2 The bootstrapper would contain and install Core.msi, then download and install one or both of the other products depending upon the user's selection. The question is, "In what form should I create and install Add_On1 and Add_On2?". Note that Core, Add_On1, and Add_On2 all need to be installed within the same directory. Initially, I was hoping to create transforms by using msitrans.exe. Then, the bootstrapper would merge the chosen transform and core.msi at installtime. However, transforms don't work with embedded cab files, and I haven't been able to create a .mst that contains files. Has anybody succeeded at creating a transform that adds files? Should I create 3 msi products and have them all install into the same directory? Other ideas? Thanks, Jon ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
