Ah, ok. Well, if the main thing is to get the size of the install, would using Burn's download capabilities add anything for you (using the DownloadUrl attribute on your Burn MsiPackage elements)? Such as only downloading the 64-bit installer if that's what they need, or only the 32-bit one? Of course you'd have to host them somewhere online where they could be downloaded from. But that would mean the user only downloads exactly what they need.
If you want to try to do the shared CAB thing, could you create a .wixlib that has the shared components. Add a Media element that specifies the name of the CAB file to create for just those components. You can use the Cabinet attribute to set the name of the CAB file and set EmbedCab to "no". http://wix.sourceforge.net/manual-wix3/wix_xsd_media.htm I haven't tried this myself, but theoretically, you could reference the .wixlib in both MSI projects, have both of them create the CAB file, but only use one of them in your bootstrapper. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multi-platform-installer-with-WiX-tp7586785p7586795.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
