Can't open resource editor in Visual C++ 2008 Pro

Question

Whenever I tried to open rc file in VC++ 2008, I get this error message.

The message said the file is corrupted, but I know the error message is not correct since I can open the resource file in another machine without any problem. I can't even open rc file from a project VC++ 2008 just created. I didn't have this problem before. I think this somehow is related to installation of VC++ 2010 Express. But when I uninstalled the express version, VC++ can't still open the resource editor. I tried several suggestions over google in vain.

Any idea how I can resolve this problem?

Answer 1

Could be the resource editor got uninstalled by your install of VC++ 2010.  

The error sounds like it is missing the resource editor, but it could be your resource file got converted to UTF-8 or some other format that VC++ 2008 doesn't recognize.  I'd try opening the resource (.RC) file using NOTEPAD.   If you do Save As, you can check the file encoding at the bottom of the save dialog.  You can save it as Unicode or ANSI depending on your needs.

If that doesn't work you could try reinstalling the full version of Visual C++ 2008 that includes MFC.  You could try the repair option.

Tom

Answer 2

Hi,

I am writing to check the status of the issue on your side.  Would you mind letting us know the result of the suggestions? 

Yi

---

Yi Feng Li [MSFT]
MSDN Community Support | Feedback to us

Answer 3

I've tried suggestions made. Repairing installation didn't work as it this time produced rc1107 error when I tried to open the rc file. I currently removed VS 2008 and am trying installing it again. If this does not work, I don't know what to do next, perhaps bombing MS?:-)

Answer 4

Unfortunately uninstalling VC++ 2010 express, uninstalling VS 2008 and reinstalling VS 2008 didn't work. I get the same RC1107 error when I tried to open rc file. I am out of idea. Please advise.

Answer 5

Hi Statcomp,

If we install the VS2008 in a fresh machine, does the issue exist?

Regards,

YI

---

Yi Feng Li [MSFT]
MSDN Community Support | Feedback to us

Answer 6

I resolved the issue with following thread.