On Tue, 26 May 2009, Sisyphus wrote: "Jan Dubois"
wrote:
> > 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 one helluva directory on my machine:
- Original Message -
From: "Jan Dubois"
> 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 one helluva directory on my machine:
13 GB
14,12
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?
> 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?
I spent some time yesterday to teach the Windows PPM build machines how to
automatically build DBD-mysql, and as a result we now have the latest
version for 5.8, 5.10 and 5.10 64-bit on the ActiveState PPM repositories.
I would appreciate if someone could give them a spin to confirm they all
work
