Visual Studio Shell Isolated error

Question

0.00/5 (No votes)

See more:

VS2010

, +

I tried to create Visual Studio Shell Isolated application, but when i run the app see following error:

"LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt"

does somebody solved this error?

Posted 16-Jul-12 6:23am

cass3000

Add a Solution

3 solutions

Solution 1

SQL

The file is corrupt.
The file is not a valid file type. An example of an invalid type is a 16-bit OMF object.

http://msdn.microsoft.com/en-us/library/7dz62kfh(v=VS.71).aspx[^]

Posted 16-Jul-12 6:44am

Wes Aday

Comments

cass3000 16-Jul-12 13:32pm

The error occurred since the project was created. I create the project and when I run it, without any changes, the error appears. So i don't think a corrupt file is causing this error.

Solution 3

I heard you need to install the SP1 for VS2010. Got the same problem ;-)

Posted 25-Sep-12 0:15am

Member 3498908

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

cass3000 · Accepted Answer · 2012-07-18T10:09:00

Solution 2

Well, finally I think I found, not the solution, but the cause:

In fact, the probably cause is corrupt files generated by VS 2012 RC. I assume this because I repeated the same steps in another PC without VS 2012 RC and it worked perfectly.

Posted 18-Jul-12 10:09am

cass3000