The Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) installs runtime components of Visual C++ Libraries required to run applications developed with Visual C++ on a computer that does not have Visual C++ 2005 installed.
v.2.0.50727.762 (v.8.0.50727.762) is typically installed with Visual Studio 2005 SP1.
v.2.0.50727.1433 (v.8.0.50727.1433) is typically installed with .NET Framework 2.0 SP1.
Installation of assemblies into WinSxS.
Runtime usage of VC, ATL, MFC libraries.
What does not
What was not tested
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Debian GNU/Linux 7.x "Wheezy" x86_64||Sep 25 2013||1.7.2||Yes||Yes||Platinum||Daniel|
|Current||Ubuntu 10.10 "Maverick" i386 (+ variants like Kubuntu)||May 28 2011||1.3.21||Yes||Yes||Platinum||Anastasius Focht|
|Show||Fedora 10 x86_64||Jan 18 2009||1.1.13||Yes||Yes||Platinum||Anastasius Focht|
|Show||Ubuntu 8.04 "Hardy" i386 (+ variants like Kubuntu)||Jul 21 2008||1.0.0||No||Not installable||Garbage||an anonymous user|
|Show||Fedora Core 6 x86_64||Sep 07 2007||0.9.42.||Yes||Yes||Gold||Peter Åstrand|
|Bug #||Description||Status||Resolution||Other apps affected|
|16577||ntdll/loader/actctx: add support of SxS assembly binding redirects||NEW||View|
|18834||Repeat installation of vcredist_x86.exe (vcrun2005 associated DLLs) deletes them permanently from the winsxs folder||CLOSED||FIXED||View|
|19811||Visual C 2005 redistributable installers create many empty directories in WinSXS||CLOSED||FIXED||View|
Always use winver "Windows XP" or later when running the Visual C runtime installer!
Don't install Visual C 2005 and later runtime using Wine winver "Windows 2000" or earlier when you intend to switch to winver > "Windows 2000" later! With winver "Windows 2000" the Visual C runtime installer will install assemblies in both, the side-by-side "WinSxS" storage and System32 directory.
If the loader fails to locate assemblies in WinSxS due to assembly manifest mismatch it fall back to load from System32 (Wine doesn't support assembly binding redirects yet). When the Visual C runtime is loaded from system32 directory in winver > "Windows 2000" mode, you will get the infamous:
This is due to checks done by the Visual C runtime itself upon load. By design, such assemblies are never to be loaded from System32 with winver set to > "Windows 2000"!
Visual C runtime uses FindActCtxSectionString API to check for
activation context support and if present it prevents any runtimes from
being loaded from system32 directory.