Answered by:
Visual Studio 2013 :Generation of the designer file for xxxxx failed: Error HRESULT E_FAIL has been returned from a call to a COM component._

Question
-
User409004464 posted
Hi,
I have asp.net Web Forms project created in VS 2012. If I open the project iv VS 2013 and modify aspx file (e.t.c add Literal to file) I get this error "Generation of the designer file for xxxxx failed: Error HRESULT E_FAIL has been returned from a call to a COM component. ".
Thanks for asnwer or sotutions.
Josef Zelinka
Thursday, November 28, 2013 4:11 AM
Answers
-
User-484054684 posted
Hi,
Please try delete the project cache and reinstall as advised below: http://rathodkrunal.blogspot.com/2011/11/visual-studio-2010-error-hresult-efail.html
Please note: I've not encountered this problem and neither ran the above command earlier. However, hope this solves your issue.Good luck!
Regards
Siva- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Friday, January 24, 2014 10:27 AM -
User281315223 posted
Have you attempted to restart Visual Studio (and try running it as an Administrator; Right-click > Run as Administrator) or Clean and Rebuild your current solution (Right-click > Clean Solution) to see if that makes any differences?
If the application itself isn't that complex, you might consider posting the code relating to it to see if we could easily reproduce the issue.
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Wednesday, February 26, 2014 4:16 PM -
User1786309542 posted
Cleaning the cache worked for me, finally. It's not where Siva pointeed to.
The cache(s) live in
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\Team Foundation
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VisualStudio
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VSCommon
and afterwards you need to run Visual Studio with the /resetuserdata switch. Be warned that this will wipe ALL of your settings.
(Running as administrator and cleaning the project didn't help, btw.)
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Wednesday, February 26, 2014 4:25 PM
All replies
-
User-484054684 posted
Hi Josef Zelinka,
Are you using any XAML in your project? If so, please check if there any syntax errors with XAML - which could also throw the aforementioned error.
Regards
SivaThursday, November 28, 2013 6:05 AM -
User409004464 posted
Hi Siva,
no. Only aspx and ascx.
Regrads
Josef
Thursday, November 28, 2013 6:09 AM -
User-484054684 posted
Hi Josef,
Could you check if this is the problem? http://stackoverflow.com/a/7712567
Regards
Siva
Thursday, November 28, 2013 6:45 AM -
User409004464 posted
Hi Siva,
no. This is for Silverlight. I have ASP.NET application.
Regards.
Josef
Thursday, November 28, 2013 7:25 AM -
User-166373564 posted
Hi Josef
As we know, Visual Studio has backward compatibility, if you create asp.net web form project in Visual Studio 2012, you can open it in Visual Studio 2013.
According to error message, I'm not sure the root of this issue. For this issue, I'd like to suggest you to recover your modification.
Regards
Angie
Friday, December 6, 2013 7:30 AM -
User409004464 posted
Hi Angie,
I have no problem with open VS 2012 project in VS 2013.
My problem has this scenario:
1. Open project in VS 2013 - OK
2. Open aspx / ascx file - ok
3. Add server control e.g. Literal to aspx/ascx
4. Save aspx / ascx - I get this error
Regards.
Josef Zelinka
Tuesday, December 10, 2013 4:37 AM -
User71929859 posted
It seems the below solution would help you. Give it a try
Monday, December 16, 2013 9:11 PM -
User409004464 posted
Hi,
I tested this solution, but no effect. I see error yet. :(
Thanks
Josef Zelinka
Monday, January 13, 2014 3:27 AM -
User1840859875 posted
I am having the same problem, and this solution also did not work for me. I have resharper installed, and after I disabled resharper, the error went away. I haven't figured out why resharper is affecting it, but at least I can work again.
Thursday, January 23, 2014 4:08 PM -
User-484054684 posted
Hi,
Please try delete the project cache and reinstall as advised below: http://rathodkrunal.blogspot.com/2011/11/visual-studio-2010-error-hresult-efail.html
Please note: I've not encountered this problem and neither ran the above command earlier. However, hope this solves your issue.Good luck!
Regards
Siva- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Friday, January 24, 2014 10:27 AM -
User1786309542 posted
I'm having the same problem. I tried adding a classname to the aspx page
<%@ Control Language="C#" AutoEventWireup="true" ... ClassName="GeneControlPage"%>
then restarting Visual Studio, and it SEEMS to be working.
I got this off of the JPHellemons web site, although the link above seems to be working. It may just be me, but VS2013's web tools seem to be awefully fragile. It seems to break if I so much as look at it funny.
(And my project/solution doesn't use XAML or Silverlight, either.)
Wednesday, February 26, 2014 3:25 PM -
User1786309542 posted
And that was just a short term fix. Deleting the cache didn't help either.
Gah.
Wednesday, February 26, 2014 3:43 PM -
User281315223 posted
Have you attempted to restart Visual Studio (and try running it as an Administrator; Right-click > Run as Administrator) or Clean and Rebuild your current solution (Right-click > Clean Solution) to see if that makes any differences?
If the application itself isn't that complex, you might consider posting the code relating to it to see if we could easily reproduce the issue.
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Wednesday, February 26, 2014 4:16 PM -
User1786309542 posted
Cleaning the cache worked for me, finally. It's not where Siva pointeed to.
The cache(s) live in
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\Team Foundation
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VisualStudio
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VSCommon
and afterwards you need to run Visual Studio with the /resetuserdata switch. Be warned that this will wipe ALL of your settings.
(Running as administrator and cleaning the project didn't help, btw.)
- Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
Wednesday, February 26, 2014 4:25 PM