Visual Studio 2010 - Design Mode Error - "Error Creating Control"

Question

User1152022145 posted

Greetings,

I am using Visual Studio 2010.  I was debugging a web application and an exception happened and VS 2010 froze.  I ended the VS 2010 in the task manager and when I went back to developing, I found on every form for every ASP.net control I get:

 

Error Creating Control -

Error HRESULT E_FAIL has been returned from a call to a COM component.

 

Also I am unable to edit  the form or add anything from the toolbox.

 

Any help on this matter will be appreciated.

 

 

 

 

Answer 1

User-529156294 posted

Hello I've the same problem and I tried everything but I cannot find any solution to this problem.

Do you fixed the problem??

Please let me know I will lose my mind with this issue.

Thanks

Answer 2

User-1747586707 posted

If it continues to happen after restarting VS, I’d recommend deleting the WebsiteCache. Chances are when the process was killed, the cache was corrupted and now it can’t be loaded properly so initialization of the control hosting system is failing.

Please let me know if it fixed the issue. Thanks.

Answer 3

User-529156294 posted

Thank you for your help.

How I can delete the website cache??

I deleted everything in "my documents" reference to visual studio and I check framework folder inside windows and I deleted everything too.

today I  tried again to work with my VS. the first hour it worked ok, but after Installed office or opened the dataset in visual I had the same error.

It possible dataset or office (access), affect something in this issue??

thanks. I working with VS more than 3 years and never I had this issue.

Answer 4

User-1747586707 posted

You can delete the project cache at "Program Files\Microsoft Visual Studio 10.0\Common7\IDE\ProjectTemplatesCache", then run "devenv /setup" to build the cache again to see if it helps.

Answer 5

User413541018 posted

I'm having this EXACT same problem.  Deleting the project cache didn't help.  Uninstalling and reinstalling VS10 didn't help either. 

Can someone recommend a place to go to get an answer from Microsoft as to what would be causing this problem?