Cause and resolution of debug DLL LoadLibrary R6034 exception

Microsoft ' s recommendation is very confusing. That's, it recommends to include a manifest file and to re-compile the project.
I recently had a problem with ' R6034 ' error message even with a manifest file already included!
in the My case, Visual Studio 2005 compiles and builds a debug-configuration of some DLLs. But, as soon as I try-to-start an application-uses that DLL the loader can ' t load the DLL and displays an error Messa GE with error code ' R6034 '.
It happened because-run-time DLLs were referenced in my DLL by some reason! As soon as I looked inside of my DLL I found II strings: 'Msvcr80d.dll' and 'Msvcr80.dll', and the 2nd one is the reason of that run-time problem.
In order to resolve the problem I added 'MSVCRT.lib' to the list of ignored libraries for debug-configuration:
[ Configuration Properties], [Linker], [Input], ' Ignore specific Library '-MSVCRT.lib

Cause and resolution of debug DLL LoadLibrary R6034 exception