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|
|Current||Debian GNU/Linux 7.x "Wheezy" x86_64||Sep 25 2013||1.7.2||Yes||Yes||Platinum||Daniel Dias|
|Show||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|
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.