Hello Peter, Hello everybody, Peter, you said:
"For #2. Use libraries instead of modules. My advice is to produce modules only if you are shipping them for consumption in a setup you have no control over. They have additional limitations when you get into patching that make them hard to service. WiX supports msm's because Windows installer supports them but I would only recommend using them as a last resort :) Dont use them to share setup logic within your own system. Take advantage of the linker to separate things into smaller projects and pull it all together in the end." Can you explain a little more what are the problems involving patches and MSMs ? I am extremely worried because in our company we have more products which share a big module. We decided to implement the installation the shared part as an MSM created with WIX (which installs files, writes registries, registers COM and permorms some extremly necessary custom actions). These decision was made because the setups for our products are done by different teams (not all of these teams using WIX), so we didn't want to share this installation as library but rather MSM (we decided one team creates the MSM and maintains it and other teams just use it). As I am part of the team which handles the MSM, I'm very woried to hear that I will probably have problems to patch it, so I would like to know what my problems could be in order to know how to avoid these problems. Many thanks. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
