Consider the following scenario. In Microsoft Visual Studio 2005, you convert a Microsoft Visual Studio .NET 2003 Microsoft Foundation Classes (MFC) application or a Microsoft Visual Studio .NET 2002 MFC application. You build the converted solution in debug mode, and then you run the MFC application. In this scenario, you may receive an error message that resembles the following:
This application has failed to start because MSVCR80D.dll was not found. Re-installing the application may fix the problem.
Note This problem is more likely to occur on a 64-bit computer or on a computer that has a very fast processor.
This problem occurs because the correct manifest data is not embedded in the MFC application.
The linker uses file time stamps to determine whether the manifest data must be regenerated during the build process. When you build the MFC application on a computer that has a very fast processor, intermediate build files are built very quickly. If the file time stamps do not change for these intermediate build files, the linker cannot detect that changes occurred. Therefore, the linker does not run the Mt.exe file to regenerate the correct manifest data.
To work around this problem, close the project immediately after the conversion to Visual Studio 2005 is finished. Then, reopen the project, and build the MFC application.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.