Another "mfc90ud.dll" not found error in VS 2008
- 0Another "mfc90ud.dll" not found error in VS 2008
I am surprised the number of times i get the same "mfc90ud.dll not found error" every time I build a vc application. Almost the same happened in vs 2005. But here is how to stop that error. Right click the project and click properties->Configuration Properties->linker->Debugging Here you will find in the right column "Generate Map File". Toggle it. yes toggle it, in some projects I have to set it to yes' and in some 'no'. Then compile, surely it will work.
Enjoy
全部回复
- 1Disable your virus scanner. It gets really exited when it sees a .exe pop up from nowhere. Asking for a .map file delays the linker enough to give the scanner enough time to not make life miserable for mt.exe.
Hans Passant. - 0
Nice ridiculously stupid post. That is not the answer. Don't try and make Microsoft look even dumber than it already does. I'm trying to figure out the answer to this as well, and your answer is not it.
- 0
It seems ridiculous but it works! I found this page by google, THX WajihUllahBaig - 0I find this error quite annoying! I'm using Visual Studio 2008 SP1 german ... yes I know, "real" developers should always use the english version ... well, anyway, the "mfc90ud.dll not found" error shows up with all new MFC projects. Basically there are only 2 ways I found so far to make this error disappear:
a) switch from "debug" to "release" configuration (which is NO solution!)
b) toggle the "Generate Map File" setting, as WajihUllahBaig descibed.
Obviously the erroneous executable is lacking the manifest, even though it should have been included by the linker. I checked the strings with Sysinternals ProcessExplorer. The erroneous executable contains the following:<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1"></assembly>
While the correctly running executable contains:<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
</requestedPrivileges>
</security>
</trustInfo>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.DebugCRT" version="9.0.21022.8" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.DebugMFC" version="9.0.21022.8" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="x86" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity>
</dependentAssembly>
</dependency>
</assembly>
Any idea how to resolve this? - 0Thanks! That actually resolved the problem.
I'm using McAfee VirusScan Enterprise 8.5i. Is this a general problem with virus scanners and compilers? I never had this before with any version of Visual Studio and MFC. Only now with the latest version (VS2008 SP1). - 0Are you asking if there are software vendors that intentionally make your machine slow and unreliable and always have an update for sale that claims to solve that problem? Yes, there are and yes, they have. You don't have to be stuck in that hamster cage.
Hans Passant.
