There are other options, involving custom actions. Using the "SourceDir" and "TARGETDIR" properties successfully, and writing a custom action that operates at the right time could potentially place files next to the MSI at install time into the installed location. That sounds like what you'd want to accomplish.
I've done something slightly similar in the past, but not quite the same. I used the "SourceDir" property and an API call into the installed application to patch a file in a very specific case where it made sense to do it this way. The pieces are definitely there in the WiX/MSI world, but as is sometimes the case with MSI, the timing of the CAs and finding the right properties are what is more difficult. Anyway, I just wanted to bring up another option to consider. In your particular case, if there aren't that many different versions and the build process can just generate those versions once and then you can deliver them to sets of customers, I would go the separate MSI route. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-setup-for-different-flavours-of-Product-tp7224149p7389659.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
