Hi, I've asked about similar issue a few days ago (on 7th January 2010): http://n2.nabble.com/Question-about-Shared-Components-and-their-Key-Paths-td4265681.html#a4265681
There is a blog post mentioning the components are tracked for each product independently: http://blogs.msdn.com/heaths/archive/2009/12/21/about-shared-components.aspx Sadly I don't know anything about Merge modules. Ondřej Zarevúcky On 31.1.2010 15:29, John Aldridge wrote: > I've read > > http://robmensching.com/blog/posts/2003/10/18/Component-Rules-101 > > and I'm still confused about something. Suppose a component gets > installed more than once, but to different places. This can happen if > several product installers include the same component (same component > GUID, containing identical resources), so we might end up with a copy of > the component's resources in both > > Program Files\ProductA, and > Program Files\ProductB > > A similar case occurs if both product installers use a merge module, but > direct the MergeRedirectFolder to different places. > > How does the windows installer keep track of this situation? If a > product is patched, do both copies of the resource get patched or just > one? If one of the two products is uninstalled, does one of the > resources get uninstalled at that time, or do both copies remain on disk > until the second product is also uninstalled? > > ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
