migration of Web application from Visual Studio 2010 to Visual Studio 2012

Question

0.00/5 (No votes)

See more:

VS2010

VS2012

We are trying to work on a web appication that was built in Visual Studio 2010 to Visual Studio 2012. The code compiles, but the controls all have an error:

Error Creating Control - (ControlName)
Error HRESULT E_FAIL has been returned from a call to a COM component.

When trying to actually run the web application in Visual Studio 2012, a window with this same error "Error HRESULT E_FAIL has been returned from a call to a COM component." shows up.

Has anyone else experienced this and if so, what steps can be taken to resolve it?

I dont have Visual Studio 2010 to open the application in.

Thank you

Posted 28-Feb-13 5:20am

Ryanm1324

Add a Solution

Comments

Sergey Alexandrovich Kryukov 28-Feb-13 12:25pm

Why would you need a COM component at all? I hope it's on the server side, isn't it?
—SA

Ryanm1324 28-Feb-13 13:49pm

I dont need a COM component.

Ryanm1324 28-Feb-13 13:53pm

Where I have a control, this error shows. So one of them is a label and instead of showing the label, it shows:
Error Creating Control - lblMsg
Error HRESULT E_FAIL has been returned from a call to a COM component.

Sergey Alexandrovich Kryukov 28-Feb-13 14:13pm

Than why do you mention it?
—SA

Ryanm1324 28-Feb-13 15:06pm

I mention it because that is the exact error showing in Visual Studio.

1 solution

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)

Ryanm1324 · Accepted Answer · 2013-03-01T04:55:00

Solution 1

Got VS 2010 and it opens fine. Just too bad its not working in 2012.

Posted 1-Mar-13 4:55am

Ryanm1324

Updated 1-Mar-13 4:59am

v2