8. January 2012 09:19
If you work with message files in your C++ project, you may have encountered the following error:
CVTRES : fatal error CVT1100: duplicate resource -- type:MESSAGETABLE, name:1, language:0x0409
fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt
I wrestled with this error recently, and for nearly 12 hours, it drove me crazy. There is a lot of speculation on the internet regarding this error, with lots of "try this or that"
Here is a concrete solution to my problem:
- I had included the message.rc file in my C++ project, along with the project's .rc file.
- The message.rc file is also listed as an included resource in the project's .rc file.
- Solution: Remove the message.rc file from your project, but leave it as an included resource in your project's .rc file.
- Reason: The resource compiler dutifully includes the message.rc. The linker then dutifully tries to link in the compiled message.res file included in the project; ergo, duplicate resource!
- If you are going to include the message.rc as a resource in another .rc file, then you should not add message.rc to your solution.
Put this down as a hard lesson learned. How hope my experience aids another developer.
18. July 2011 08:37
I cleaned up my hard drive several weeks ago. One task that I accomplished was removing a splattering of Windows SDK installations. I think I had six different versions installed. It certainly felt good and freed up some disk spaced consolidating everything to Windows SDK 7.1.
Except, I tried to build a setup package of a program I had completed. It would not builld. Both VS 2010 and VS 2008 informed me that it could not find the msi installer AND the WindowsSDKDir was pointing to an invalid location. Hmm...
Not to fear. I did a repair of VS 2008 and VS 2010 and all is well.
One thing I did learn, do not repair VS 2008 SP1 from the installation media: "Do not repair VS 2008 SP1 from installation media". I followed the same logic when repairing VS 2010. Repair the systems from the Add-Remove programs menu item (when using XP.)
Unfortunately, I am back to 3 installed versions of the Windows SDK, but that's OK. Everything is working now and I am not going to mess with it.
31. May 2011 08:59
I have found the new help viewer supplied with the VS 2010 Service Pack to be fairly worthless. My primary problem has been that I can only follow content by clicking on the TOC treeview. Clicking on internal hyperlinks in the help document window brings up a raw xml file that tells me it can't find the content.
I've managed to come up with a procedure to fix the problem. The solution fixes the issues of dead hyerlinks in documents while using local content.
- Open the MS Help Viwer 1.1.
- Start the Help Library Manager
- Switch to online content
- Close down the manager and help viewer
- Start up VS 2010
- Open a project and a c# file
- Hilight a c# keyword and press F1
- You should see online content
- Now, while in VS 2010, click Help->Manage Help Settings
- Switch back to local settings
- Shutdown the help viewer and VS 2010
- Now you may start help from VS 2010 or by clicking the documention link in the start menu.
Internal links can now be followed correctly. You will also see that local style sheets are now correctly applied to the local help content.