Can someone please detail how Merge Module versioning is supposed to work?
I cannot find guidance anywhere for Merge Module versioning (especially in
WiX).  I've seen WiXLibraries, so if that would work better, please tell me
how.

The scenario, which I believe is common:  Certain shared files and registry
settings ought to always be the most up-to-date, installed by any of three
MSIs that contain the shared files.  Any one MSI may be installed alone OR
multiple MSIs may be installed to the same machine.  Uninstallation should
not remove components if they are still used by other installations.
Installation with older shared file/registry settings (as a whole) should
not overwrite newer versions.

I believe that Merge Modules exist for this purpose.  I don't believe that I
need a separate MSI and boot-strapper executable to achieve this
functionality.

I feel pretty comfortable in WiX generally, but I am really struggling with
this.

Thanks.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to