I'd definitely include the policy modules. I took them out after reading the referenced comment in the WiX doc, and then a Visual Studio update broke our installation. Visual Studio was building against one version of the runtime and the merge modules were distributing another. Re-adding the policy merge module fixed things.
Rob On 18/05/2011 13:49, Francisco Gabriel Malbrán wrote: > You may also consider installing the policy redistributable merge module. > Although WiX's documentation says you probably shouldn't need it, it does > not say that you will *definitely* not need it. > I haven't found much information on the policy merge module, but enough to > know that it basically serves the purpose of redirection when a different > (lower) version of the redistributable is asked for and you happen not to > have exactly that one. > > People in the list will probably know more on the subject, but I just wanted > to pointed out. > > Regards > > 2011/5/18 Pally Sandher<pally.sand...@iesve.com> > >> Make sure the machine you build your package on has that version of Visual >> Studio installed& it will have the corresponding merge modules in the >> Common Files area then just link them as usual. >> Visual Studio installs the same version of merge modules as itself. It >> doesn't keep a repository of previous versions or anything. >> However you would probably be better off submitting the specific version of >> the runtime merge modules to your source control& then linking them into >> your package from there. If your binaries are built on one machine& your >> package on another you may find they get out of sync due to Windows Updates >> & your app then fails to launch after installation with a Side-by-Side error >> (someone posted this exact same issue not too long ago). If updates to your >> machines are controlled by your company using WSUS or something similar& >> you can be 100% sure no one will approve any Visual Studio 2008 updates >> which will change that version then you could live with the ones in Common >> Files but personally I wouldn't risk it. >> >> Any reason why you need to stick to a specific version? Most up to date >> version as of last month is 9.0.30729.5570 as far as I can see which >> resolves some pretty major security exploits. >> >> Palbinder Sandher >> Software Deployment Engineer >> T: +44 (0) 141 945 8500 >> F: +44 (0) 141 945 8501 >> >> http://www.iesve.com >> **Design, Simulate + Innovate with the<Virtual Environment>** >> Integrated Environmental Solutions Limited. Registered in Scotland No. >> SC151456 >> Registered Office - Helix Building, West Of Scotland Science Park, Glasgow >> G20 0SP >> Email Disclaimer >> >> -----Original Message----- >> From: Brad Lemings [mailto:b...@rebit.com] >> Sent: 18 May 2011 03:22 >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] How to use a particular version of runtime >> mergemodules? >> >> >> All of our software - both 3rd-party and in-house - is built against a >> particular version of the VS/VC runtimes - specifically "9.0.30729.4148". >> >> How does one utilize merge modules in Wix sources using a particular >> manifest/version of the VS/VC runtimes? >> >> Thanks, >> Eric. >> >> >> ------------------------------------------------------------------------------ >> What Every C/C++ and Fortran developer Should Know! >> Read this article and learn how Intel has extended the reach of its >> next-generation tools to help Windows* and Linux* C/C++ and Fortran >> developers boost performance applications - including clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> >> >> ------------------------------------------------------------------------------ >> What Every C/C++ and Fortran developer Should Know! >> Read this article and learn how Intel has extended the reach of its >> next-generation tools to help Windows* and Linux* C/C++ and Fortran >> developers boost performance applications - including clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > ------------------------------------------------------------------------------ > What Every C/C++ and Fortran developer Should Know! > Read this article and learn how Intel has extended the reach of its > next-generation tools to help Windows* and Linux* C/C++ and Fortran > developers boost performance applications - including clusters. > http://p.sf.net/sfu/intel-dev2devmay ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
