> I'll look into this problem. You may also want to check and see if any of these
apply to your problem.
thanks, looking at that link, it looks like problem #5 might be the same
^Problem #5: Exception in ResourceCompiler.exe
ResourceCompiler.exe is a managed application that we wrote to automatically create C# string resources and matching C++ resources (with matching header files) for cross project message availability. Very nice. And very broken. As with many internal tools, the error handling sucks, but it was easy to see from the exception that one of the required input files was missing. Backtracing this, it turns out that the SDK tools "MC.exe" (Message Compiler) and "RC.exe" (Resource Compiler) were supposed to run and spit out some stuff. The problem is that (you guessed it) the locations for these utilities have changed with VS2008 and the batch file which calls them was silently skipping those steps. Double doh!
Now I'm on the crux of indecision. The "pure" way to solve this problem without affecting anything in source control is just to copy these (and other related) files from their new location in the v6.0Ain SDK folder (which we already mapped to [app]VCPlatformSDK) to the old location (which was [app]Common7in). The "correct" way to solve this problem is to fix the stupid batch file to test for the existence of mc.exe and rc.exe and if they don't exist, try the other folder. If if they don't exist there, fail the build where the actual problem occurred rather than letting it continue and fail obscurely somewhere else. ^
i dont know if it is related, ill have a go at fixing it though.