On Tue, 26 May 2009, Foo JH wrote: > > Running the *appropriate* vcredist_x64.exe fixes the problem. (The > > appropriate one being the one for VC++ 2008, not the one for VC++ > > 2005.) > Does this mean that if there is an existing app which ref the VC2005 > dll, there will be a collision problem?
No, the DLLs have different names, e.g. MSVCR80.dll for VS2005 and MSVCR90.dll for VS2008 (MSVCR70.dll was for VS.NET and MSVCR71.dll for VS 2003). The confusion was just the name of the *installer* for the redistributable DLLs, which doesn't contain a version number. But the files being installed by the identically named installers are different. You can actually install different versions of MSVCR80.dll on the same machine; they go into different directories under C:\Windows\WinSxS (the side-by-side installation directory). That's why applications linking against MSVCR80.dll need a binding manifest so that the OS knows which one of potentially multiple copies of MSVCR80.dll should be loaded for the application. Cheers, -Jan _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
