VC++: KB971090 and selecting Visual C Runtime DLL dependencies

Question

As you might know, Microsoft recently deployed a security update for Visual Studio: KB971090.

Among other things, this updated the Visual C Runtime DLL from version 8.0.50727.762 to 8.0.50727.4053.

So after this update, everything I compile that uses the runtime dynamically linked, gets their dependencies updated to the new runtime.

Of course, for new applications it is fine to update to the new, presumably more secure, version.

But I would also like to be able to retain the old dependency - for example, I might like to build a fixpack that only require a single DLL to be replaced (if I try to do that after the update, I will get the dreaded "This application has failed to start because the application configuration is incorrect." unless I also distribute the updated runtime).

Is there any way to do this, or will I need to retain two installations of Visual Studio: one updated and one non-updated?

Prolific

See also: netscantools.blogspot.com/2009/08/… – Prolific

I have a very similar question, but I am more concerned about using different version of the c runtime library in a single executable. see #1239241 – Sofar

Cool. This is now the 3rd hit on Google for KB971090. – Deceive

Answer 1

You can specify the version by using the workaround found here

Inconvenient

Answer 2

You can turn off autogenerated manifest and include your own with the library version you need.

For example:

<dependency><dependentAssembly><assemblyIdentity type="win32" name="Microsoft.VC90.DebugCRT" version="9.0.21022.8" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity></dependentAssembly></dependency>

Eyre

This implies you'd use the new headers and stub libraries at build time and the older DLL only at runtime. Is this supported by Microsoft? – Interment

Your example refers to DebugCRT. That one is NOT redistributable. – Martinemartineau

@Nicolás: This is a sample. You can refer any assembly in that way. – Eyre