Yes - that's what merge modules do. They are the same resource component in a package used to build multiple products to keep the sharing working properly. Put the shared components in merge modules to be safer. If you're all WiX there are WiX fragments.
This assumes that the resource is the same actual thing. It's asking for trouble to have completely different resources with the same component id. Phil Wilson On Thu, Dec 5, 2013 at 10:50 PM, uni <unigauld...@gmail.com> wrote: > Hi, > > > > We got two different products, say product A and product B. > > > > Product B's msi is identical with product A's except the UpgradeCode is > different, and lacking some features. > > Product B's source code is based on Product A's, so the components are the > same as Product A's. > > Product A and Product B can be installed on the same computer, just like > visual studio 2008 and visual studio 2010 could coexist. > > Product A and Product B will be installed on different directories. > > > > Is it safe to author like that? > > > > Thanks, > > > > Gauldoth > > > ------------------------------------------------------------------------------ > Sponsored by Intel(R) XDK > Develop, test and display web and hybrid apps with a single code base. > Download it for free now! > > http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
