ATL Security update broke compatibility for DLLs depending on the older version

tags:

views:

312

answers:

3

+1 Q:

ATL Security update broke compatibility for DLLs depending on the older version

The recent ATL security update updated the C++ runtimes to version 8.0.50727.4053. Unfortunately, this update broke one of our DLLs that dynamically links to the runtime, as we only have 8.0.50727.762 available to us on the target machine (we don't even use ATL).

Is there a way we can get Visual Studio to dynamically link to the older DLL? I'd like to avoid statically linking if possible.

A:

Copy the requisite DLL versions directly into your executable's directory, it is searched first during dynamic linking.

David Wilson 2009-08-03 14:32:44

The assembly uses side-by-side linking, which first checks the WinSxS directory for the DLL specified in the manifest. I've tried manually editing the manifest but it gives SxS configuration errors.

Ron Warholic 2009-08-03 15:08:13

sounds like the question should be "how do I edit the manifest to allow my library to work with other versions of the C++ runtime" then.

jalf 2009-08-04 11:00:50

A fair assessment, however I first wanted to probe to see if anyone had experienced growing pains with the ATL update like we have.

Ron Warholic 2009-08-04 13:18:29

A:

I don't know if this is feasible but have you tried having your customers install the redistributable package?

Motti 2009-08-04 09:33:20

I wish we could but the system is an integrated FPGA processor and a workstation that has a tightly controlled environment. If we wanted to upgrade runtimes we'd need to do a lot of extra work.

Ron Warholic 2009-08-04 13:16:32

+2 A:

Another solution is forcing VS to link against the old versions of the WinSxS DLLs as explained in this article.

Motti 2009-08-31 08:47:36

ansaurus

tags:

views:

answers:

ATL Security update broke compatibility for DLLs depending on the older version

related questions