Home/ Questions/Q 3222736
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T16:01:32+00:00

I am having a problem with building an application in Visual Studio 2008. I

  • 0

I am having a problem with building an application in Visual Studio 2008. I have declared the following in my project properties:

_BIND_TO_CURRENT_MFC_VERSION=1
_BIND_TO_CURRENT_CRT_VERSION=1
_BIND_TO_CURRENT_ATL_VERSION=1

When I build my application in VS2008 it generates an intermediate.manifest file which contains:

<dependentAssembly>
  <assemblyIdentity type='win32' name='Microsoft.VC90.CRT' version='9.0.30729.1' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' />
</dependentAssembly>

Now, this machine has newer C runtime DLLs installed (version 9.0.30729.4148 can be found in the WinSxS folder). The pre processor definitions above are supposed to tell VS to use the latest runtime DLLs, but it doesn’t appear to be doing so. Is anyone able to explain why dev studio won’t show the newer version of these DLLs in the manifest? I can build the same application on other machines and get the right number in the manifest file, so it must be something peculiar to the setup of this one machine, but I don’t know what.

The machine where I am having the problem is a Windows 2003 SP2 server. Can anyone shed any light on how dev studio works out what the latest runtime version is?

Thanks,
Al.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You indeed have an old version of the CRT. The version number is set in the vc\include\crtassem.h include file. Windows Update should have given you the security update that was released in July of last year. It also updates the CRT .h and .lib files. Maybe you got that release from an installer of another program.

    If you don’t want to turn on Windows Update then you can get the security update from here. Beware that the download it starts is rather large.

    • 0