Both products install the driver into the same directory. Afterwards it is installed with a custom action.
The rest of the files go into other directories... > -----Ursprüngliche Nachricht----- > Von: Christopher Painter [mailto:chr...@deploymentengineering.com] > Gesendet: Freitag, 12. November 2010 14:30 > An: General discussion for Windows Installer XML toolset. > Betreff: Re: [WiX-users] Usage of Merge Module for multiple > projects(updates etc.) > > Does Product A and Product B install to the same directory or > different directories? > > In the context of your question, merge modules are merely > collections of components that get merged into your > installer. The merge module no longer exists once merged. > Their components behave just like any other components you > authored directly into the installer. > > Christopher Painter, Author of Deployment Engineering Blog > Have a hot tip, know a secret or read a really good thread > that deserves attention? E-Mail Me > > > > ----- Original Message ---- > From: Tobias Erichsen <t.erich...@gmx.de> > To: wix-users@lists.sourceforge.net > Sent: Fri, November 12, 2010 5:55:28 AM > Subject: [WiX-users] Usage of Merge Module for multiple > projects (updates etc.) > > Hi everyone, > > I have put a device-driver installation into a merge module to be used > in several MSI-installers for multiple applications using that driver. > > The driver is always backwards-compatible (as is the > installation), but > a newer application might be depending on the feature of the newer > driver version. > > I have found lots of information about updates (major, > minor...) concerning > MSI, but not a lot concerning how the update will behave with the > merge-modules. > > For example: > I have an MSI for Product "A" containing the merge-module of > my driver with > version "1.0.0" > I have a second MSI for Product "B" containing the > merge-module of my driver > with a newer version "1.1.3" > > When someone is now installing Product "A" and he has already > installed > Product "B" which contains > a newer version of my merge-module with the newer driver - > will the newer > driver be overwritten > by the older version? How can I prevent this? > > Best regards, > Tobias > > > -------------------------------------------------------------- > ---------------- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > -------------------------------------------------------------- > ---------------- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
