I'm creating four MSI's now, three MSI's are setting up each an WebService, and, one main MSI that installs an clientapplication. Today, these are separate MSI's, and will probably be that for those who want to install separately.
But, the main MSI, we want to be made so it includes the other MSI's somehow, preferably all linked in the main MSI file, so everything can be installed, and choosed from an featuretree in that installation. But, it seem that this might not be very easy? If I choose bundle, I will get an EXE, not an msi file (since MSI supposedly cannot start an msi?) Bundle will not include the MSI either, they need to reside next to the exe-file, or be downloadable from somewere. Neither of those we want.. But, are there other ways of doing this?, is it kosher to make MSM modules AND MSI modules for the service packages?, and include the MSM modules inside the main one? Or, is it better to include the wix sources from the service packaged into the main MSI, and also use them in their own msi's? I guess there will be problems with component id's, and I will get problems with product codes, updates etc.. :( -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Main-MSI-with-sub-msi-s-tp7595221.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
