[Qt-interest] (solved) Mismatched VC90 CRT versions in manifest file

[Oliver.Knoll at comit.ch]

David Ching wrote on Friday, January 29, 2010 4:42 AM:

> > ...
> Regardless, if both your Qt DLL's and your .exe depend on the RTM
> redistributables, yes, you do need to redistribute the RTM version. 
> Trouble is, the vc\redist folder containing these is updated to
> 9.0.30729.4148, and there is no easy way of getting the RTM ones back
> (that I could find), unless you had saved them from before the update
> occurred. 

Sorry to jump right into this thread, I just roughly followed it. But the version numbers and VS runtime DLLs, that rang a bell. I remember having read about a bug that some Visual Studio (I think 2008) had a wrong version number set somewhere, which caused applications to link against the wrong (older) C/C++ runtime DLLs. But the ones installed by the vcredist.exe were newer, so depending on how you linked your app it might run on the target machine or not (depending on whether these older runtime DLLs already happened to be there or not).

Unfortunatelly I can't remember /where/ exactly I read this, I think in some comment of some MSDN article (doh!). But I think this issue got solved by some Visual Studio service pack (or was even caused by such one).

Oh, I just found some reference to this issue, but it affects SP1 for VS 2005 (not 2008!): http://msdn.microsoft.com/en-us/library/ms235624%28VS.80%29.aspx: Comment VS2005 SP1 installs wrong MSMs: "WARNING: VS2005 SP1 installs some MSM files with version 8.0.50727.42, but builds your code against 8.0.50727.762. WHen you deploy your app on a raw WinXP machine, it gets the 8.0.50727.42 redistributables from the MSMs, which won't work with your installed app."

Bottom line: there *have* been issues with redistributing C/C++ runtime DLLs, and it is not always your fault when your app won't run on the target machine ;)

Cheers, Oliver  

-- 
Oliver Knoll
Dipl. Informatik-Ing. ETH
COMIT AG - ++41 79 520 95 22