I can't find any documentation on best-practices when creating either merge modules or wixlibs, only procedure documentation on how to create them.
Let's say I create a wixlib (or msm) with multiple components that make up a large C++ library. Someone making an application with that library can then use the wixlib and only write installation code for his own app files, instead of having to also define the installation of the library. But where would the library be installed? Would the wixlib need to have a Directory under (say) Common Files where the library would go? Or can the wixlib provide a way for the application wxs to decide where the library would be installed? But then there's a problem: two applications importing the same wixlib could install the same components (with same GUID) in different directories. As far as I know that means only the first one would get installed, the second would see the component is already installed (identified by GUID) and do nothing. Does anyone have experiences to share? -- Nicolás ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
