I have regularly this issue under Visual 2005 or 2008 :
When I compile a bunch of DLLs (native C, C++, managed), sometimes, few of them don't link correctly with some microsoft debug DLLs. The output does not mention anything (no warning, no error). I can't be aware until I launch my program and get a "Module not found exception" without more explanations.
When I open my Dlls with Dependency Walker, some are missing MSVCR90D.DLL and MSVCP90D.DLL. If i am in a lucky moment, i just have to rebuild the corrupted dll to get a valid one. In the worst case, the rebuild produces another corrupted dll, until a mysterious moment (hours or days later) when a got a valid dll... sounds crazy, isnt it ?
The valid dll have this kind of path :
*c:\windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.30729.1_x-ww_f863c71f\MSVCP90D.DLL*
This is driving me insane!... Any ideas ? Thanks.