OFF-TOPIC - this has to do with compilers and manifests, but does refer to this problem.
I have experienced a similar issue with a client's product I was working on. With VS 2008 SP1, a new revision of the C runtime/ATL/etc. DLLs are used. Apps compiled with this will have this registered in their manifest as the version they want to run against. If your app is compiled to run using the manifest, it will be set as a resource in the exe/dll. You can actually use VS 2008 to open the exe/dll and review the resources. The manifest will show up as binary, but can be read with a bit of practice, or copied into text editor. There you should see which version of the C dlls it is referencing. One thing you can do as a work-around is to create your own manifest file, basically the same as is saved as a resource with the specific version of the runtime you want, and put that with the exe/dll. This will act as an override over the version in the resources. The real fix of course is to make sure that you have the same version of the runtime merge modules on the machine that is building the executables and the machine that is creating the installer. You can apply the VS 2008 service pack, or copy the relevant merge-module to the installer build machine. With Orca you can examine the version of the files in the merge module to make sure that they match the version that the executables want to run against. I was suffering with this exact same issue, when dealing with my client that was running VS 2008 without the service pack in various tests. Once I found out how to determine the versions that were compiled into the executables vs. what was installed was I able to resolve this. Andreas -----Original Message----- From: William Bardwell [mailto:bardw...@curl.com] Sent: November-19-09 9:30 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 2902 error installing with VS 2008 SP1 CRT merge modules on Vista/Win7 > William, > > We have seen serious problems with this merge module. I think there's an unav > oidable problem with per-user installations if you use it. In at least one of > our setups, we use an executable file to install the VS 2008 support, instea > d of the merge module. We do not use per-user installations, just per-machine. (And changing ALLUSERS from 2 to 1 didn't help.) We have been trying to avoid the exe's because they are huge, we only need msvcr90.dll. William Bardwell wbard...@curl.com ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
