I griped in a previous blog that the warning popup didn't give you enough information about where it was trying to read the C Runtime Library from and luckily SysInternals' Process Explorer program does. When you get that popup, start up Process Explorer and you'll see multiple instances of msvcr80.dll. Find the one that is not in the SxS area and delete it and these errors will go away:




On to the next PITA XP error and this time Process Explorer didn't help since the program never pauses. FileMon also didn't help to see what file it's trying to access (I think it's actually trying to touch a cursed COM object that isn't registered properly but I have no clue which one it is). If anyone has tips on hunting these errors down, let me know. Google didn't turn anything up for this error when running a MS Windows Deployment Project:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe -v /MyWebProj -p F:\work\Ektron\CMS400v6\MyWebProj -u -f -d F:\work\Ektron\CMS400v6\ASSEMBLYSRC\MyWebProj_deploy\Debug\
ASPNETCOMPILER : error ASPCONFIG: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Done building project "MyWebProj_deploy.wdproj" -- FAILED.

Edit: FYI, this last error was because I didn't include these directories in VS.2005's Tools/Options/VC++Directories list:
$(SystemRoot)\System32
$(SystemRoot)\System32\wbem
Yep, what a cryptic error again :-P