I once upgrade my 2002 project to 2005, and it worked without any problem.
But after I change the charset from mbcs to Unicode, then when I run the debug version, Windows informs me that "cannot find MFC80ud.dll". After hours of research and compared with the default project created by 2005, I found that the problem was due to manifest file in ".rc" (It was auto-generated by 2002):
/////////////////////////////////////////////////////////////////////////////
//
// RT_MANIFEST
//
IDR_MANIFEST RT_MANIFEST "res\\Math.manifest"
after deleting the above lines, the app runs. (the manifest only contain stuff about "Microsoft.Windows.Common-Controls", and was generated by 2002 automatically when I created the project)
I know 2005 use embedded manifest, but I don't know why my app failed only in Unicode mode, and why there is no warranty about these manifest issue in the upgrade engine since 2005 no longer require externel manifest
PS:the content of the Math.manifest
< xml version="1.0" encoding="UTF-8" standalone="yes" >
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="Microsoft.Windows.Math"
type="win32"
/>
<description>...</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
</assembly>

Can't find MFC80ud.dll error
specialk92282
KH Tan
http://blog.kalmbachnet.de/ postid=54
AFAIK in you situation the migration to 2005 creates a new external manifest, but this is ignored because you had a previous (and no longer valid) manifest inside your application. This caused the MFC80 DLL die reject to load.
Merge the new manifest and your old one and place it again inside. I not so firm with the new techniques. AFAIK there are new tools in 2005 to link manifests to an exe. May be other guys have more info's about that.
Craig Paterson
task manager.Is this any licencing issue or anything ...please help me...u can reach me at rajesh.kamath@hotmail.com
Anson Goldade
Sorry for my ignorance, the updatelog.xml clearly state the manifest issue. I ought to pay more attention to those warnings.
pro-logic
I also met this problem, but the phenominence is different.
When I just installed the Visual Studio, I can excute the solution that is created by MFC without any modification, for example a empty Dialog based MFC programme. But now, evern i didn't do any modification to the code, when I create an empty Dialog based on MFC, It can't be excuted. The error given by Visual Studio is lack of "MFC80UD.DLL"
Can any one help me Thanks
ParagB
Hi TangQing,I have came across the same problem with you.
When I start debugging a default created MFC dialogue box solution with "Shared dll" and without my modification, a pop-up message box said that "Can not find MFC80UD.DLL", but a checked the derectory "C:\WINDOWS\WinSxS\x86_Microsoft.VC80.DebugMFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_c8452471", and was sure MFC80UD.DLL was there.
But I found that when I keep doing "Rebuild" and "Start debuging" for several times, this error will not show up. And when I went on doing that, the error show up again....
That is strange.