Visual C++ Redistributable Package

What works

Installation of assemblies into WinSxS.

Runtime usage usage of VC, ATL, MFC libraries.

What does not

Workarounds

What was not tested

n/a

Hardware tested

Graphics:

• GPU:
• Driver:

Additional Comments

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:

­R6034: An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for moreinformation.

­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"!

The 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.