locked
Visual Studio Express 2013- designer doesn't load

    Question

  • Hi All,

    I have just freshly installed VS Express 2013, on Windows 8.1 Pro. All updates are installed. I have already had VS 2005, 2010 and 2012 installed on this PC. When I create new project (any kind, for example Visual C# -> Store Apps -> Windows Apps) I am unable to use the designer (for MainPage.xaml). It always returns the same Unhandled Exception error (included below). I tried to repair VS 2013, to uninstall it and install again... everything fails. Please help.


    EDIT: I created new project of the same type (Visual C# -> Windows Store) in VS Professional 2012 and get exactly same error when tried to open .xaml file in designer.
    My other regular windows forms project work without any issues and load designer flawlessly.


    System.Runtime.InteropServices.COMException
    The app didn't start. (Exception from HRESULT: 0x8027025B)
       at Microsoft.Expression.HostUtility.AppPackage.AppPackageNativeMethods.IApplicationActivationManager.ActivateApplication(String appUserModelId, String activationContext, ActivateOptions options, Int32& processId)
       at Microsoft.Expression.HostUtility.AppPackage.WrtUtility.ActivateApplication(String appUserModelId, String activationContext, Object site)
       at Microsoft.Expression.HostUtility.Platform.AppContainerProcessDomainFactory.ActivateApplicationInternal(String appUserModelId, String activationContext, Object site)
       at Microsoft.Expression.HostUtility.Platform.AppContainerProcessDomainFactory.CreateDesignerProcess(String applicationPath, String clientPort, Uri hostUri, IDictionary environmentVariables, Int32& processId, Object& processData)
       at Microsoft.Expression.DesignHost.Isolation.Primitives.ProcessDomainFactory.ProcessIsolationDomain..ctor(ProcessDomainFactory factory, IIsolationBoundary boundary, AppDomainSetup appDomainInfo, FrameworkName targetFramework, String identifier, String baseDirectory)
       at Microsoft.Expression.DesignHost.Isolation.Primitives.ProcessDomainFactory.CreateIsolationDomain(IIsolationBoundary boundary)
       at Microsoft.Expression.HostUtility.Platform.AppContainerProcessDomainFactory.CreateIsolationDomain(IIsolationBoundary boundary)
       at Microsoft.Expression.DesignHost.Isolation.Primitives.IsolationBoundary.Initialize()
       at Microsoft.Expression.DesignHost.Isolation.Primitives.IsolationBoundary.CreateInstance[T](Type type)
       at Microsoft.Expression.DesignHost.Isolation.IsolatedObjectFactory.Initialize()
       at Microsoft.VisualStudio.ExpressionHost.Services.VSIsolationService.CreateObjectFactory(IIsolationTarget isolationTarget, IObjectCatalog catalog)
       at Microsoft.Expression.DesignHost.Isolation.IsolationService.CreateLease(IIsolationTarget isolationTarget)
       at Microsoft.Expression.DesignHost.IsolatedDesignerService.CreateLease(IIsolationTarget isolationTarget, CancellationToken cancelToken, DesignerServiceEntry& entry)
       at Microsoft.Expression.DesignHost.IsolatedDesignerService.IsolatedDesignerView.CreateDesignerViewInfo(CancellationToken cancelToken)
       at Microsoft.Expression.DesignHost.Isolation.IsolatedTaskScheduler.InvokeWithCulture[T](CultureInfo culture, Func`2 func, CancellationToken cancelToken)
       at Microsoft.Expression.DesignHost.Isolation.IsolatedTaskScheduler.<>c__DisplayClassa`1.<StartTask>b__6()
       at System.Threading.Tasks.Task`1.InnerInvoke()
       at System.Threading.Tasks.Task.Execute()


    • Edited by storm_blast Thursday, December 11, 2014 11:52 AM
    Thursday, December 11, 2014 9:27 AM

Answers

All replies

  • Hi Storm_blast,

    Please find the C:\Users\{your account}\AppData\Local\Microsoft\VisualStudio\12.0\Designer\ShadowCache folder, remove the contents in ShadowCache folder and try visual studio again.

    Please let me know if you have any concerns.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Friday, December 12, 2014 2:45 AM
    Moderator
  • Hi Herro Wong

    Thank you for help but unfortunately it didn't help.

    I remove everything from this folder, run VS 2013, created new Visual C# - Store Apps - Windows Apps project. Double clicked MainPage.xaml -> same error appeared and designer didn't load. 3 items have been created in ShadowCache folder.

    EDIT: I did the same for VS 2012 - still same error.

    • Edited by storm_blast Friday, December 12, 2014 8:42 AM
    Friday, December 12, 2014 8:40 AM
  • Hi Storm_Blast,

    I found a user has solved this issue by restarting the computer, did you mind to try this?  https://connect.microsoft.com/VisualStudio/feedback/details/773539/cannot-load-designer-in-any-project-designer-process-terminated-unexpectedly.

    If this doesn’t work either, feel free to let me know. I will ask visual studio expert to look into this thread.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Friday, December 12, 2014 8:50 AM
    Moderator
  • Sure, I will try everything.

    So I cleared ShadowCache folder, rebooted PC, made sure that ShadowCache is still empty (it was). Started VS Express 2013, new project as usual, opened MainPage -> same error.

    I believe that error described in the article which you lineked is a bit different. It refers to exception

    System.Runtime.Remoting.RemotingException [3432] 

    my exception is:

    System.Runtime.InteropServices.COMException
    The app didn't start. (Exception from HRESULT: 0x8027025B)


    By the way, since my problem started, I restarted my PC several times before, installed several Windows updates (at least one was to VS 2013), repaired VS 2013, uninstalled it and installed again.

    It is fresh PC, just bought and has fresh installations of each VS. I never managed to make VS 2013 Windows Store projects to open in designer. Same wit VS 2012.

    I appreciate your help.

    • Edited by storm_blast Friday, December 12, 2014 1:05 PM
    Friday, December 12, 2014 9:22 AM
  • Hi Storm,  

    Thanks for your post.

    On your current client, you only occurred this error when creating Windows Apps project using VS 2013 Express or VS 2012 Professional? There’s no issue to create other types of project using VS 2013 or VS 2012?    

    This issue only happened on your current client? If you have another Windows 8.1 client which has VS 2013(or VS 2012) installed, the create Windows Apps project using VS 2013 works fine in that client?


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, December 15, 2014 7:31 AM
    Moderator
  • Hi John,

    On your current client, you only occurred this error when creating Windows Apps project using VS 2013 Express or VS 2012 Professional? There’s no issue to create other types of project using VS 2013 or VS 2012? 

    Correct. On VS 2012 - I can open all my old C# Windows Form Application or create a new one and edit in designer. Only Windows Store projects fail to start designer.

    In VS 2013 I have only Windows Store apps templates. The problem is probably only with .xaml files.

    Just to clarify - the error appears not when I create a project but when I open .xaml file in designer mode (default mode when I double click it).

    This issue only happened on your current client? If you have another Windows 8.1 client which has VS 2013(or VS 2012) installed, the create Windows Apps project using VS 2013 works fine in that client?

    I don't have any other PC at workplace to test it. I may try ad install it at home later today if you wish, but it would be a bit different experience at windows home and without other versions of VS installed. But, to be honest, I don't really see how would it bring us closer to solution if we find out that VS 2013 Express starts designer correctly on other PC ? I guess that there are thousands of such PCs everywhere, otherwise this topic would be much more popular. I searched a lot of forums myself and the only "solution" which appeared was to "reinstall windows 8"...



    • Edited by storm_blast Thursday, December 18, 2014 3:07 PM
    Monday, December 15, 2014 9:01 AM
  • Thanks for all your support so far. Is there anything else that I could do to help you to help me ? "Turn it off and on again", which as it appears is the most common attempt of help on these forums, doesn't work for me, even if by "turn off" you understand uninstall VS.
    Tuesday, December 16, 2014 1:43 PM
  • Update:

    I uninstalled VS 2013 Express. I will focus on VS 2012 Pro - will try to fix it first as it has the same issue (and both issues probably have the same root cause).

    I "repaired" VS 2012, restarted PC - same error still exists, as quoted in first post.

    I checked Event Log, it contains following entrance:

    Activation of app App.abcd5e58f.a70a3.a4dac.a99ca.a9155d48bf42b_8wekyb3d8bbwe!Designer.App failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional information.

    I checked  "Microsoft-Windows-TWinUI/Operational log for additional information" and as expected (Microsoft typical) the additional information is as follows:

    Activation of the app App.abcd5e58f.a70a3.a4dac.a99ca.a9155d48bf42b_8wekyb3d8bbwe!Designer.App for the Windows.Launch contract failed with error: The app didn't start..

    EDIT: I tried r-click on .xaml file and open it in Blend and it returns exactly same error message. Blend works perfectly for JavaScript project for .html files.
    • Edited by storm_blast Thursday, December 18, 2014 3:17 PM
    Wednesday, December 17, 2014 4:05 PM
  • Hi Storm_blast,

    Did you install the visual studio 2012 update 4? If not, please refer to the following link to install it. http://www.microsoft.com/en-hk/download/details.aspx?id=39305.

    And you can also perform a clean boot and retry the visual studio again. This can help us to avoid conflict from other software. https://support.microsoft.com/KB/929135?wa=wsignin1.0.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. Click HERE to participate the survey.

    Friday, December 19, 2014 1:58 AM
    Moderator
  • Hi Herro Wong,

    Thanks for your reply.

    Yes, I have update 4 for VS 2012. VS 2013 Express had it by default.

    I tried clean boot (switched off all startup programs and all services except MS services. Rebooted. Created new project as usual -> same error still exists.

    I don't know anything about the technology behind VS and designers, but it looks like some kind of common engine that powers all XAML designers for all versions of VS might be corrupted and what's worse, it looks like this engine has not much to do with VS installation. But that are just my feelings.

    Friday, December 19, 2014 10:26 AM
  • bump



    Other people have same issue:

    https://social.msdn.microsoft.com/Forums/en-US/276f8170-21f9-4f2d-a96e-9d4e84d10511/an-unhandled-exception-has-occured-xaml-designer

    Tuesday, January 6, 2015 9:07 AM
  • Hi storm_blast,

    I'm working on the XAML Designer team and would like to follow up on this issue directly with you to try and reproduce it on your machine/environment, maybe over a Skype or a shared screen call. Once we find a solution we will post the results here. Could you please reach me at Nikolami at Microsoft dot com if you don't mind? I'm sorry for the issue you're experiencing, and thank you for being vocal! (also noticed your comment on https://connect.microsoft.com/VisualStudio/feedback/details/1076217/windows-phone-8-1-xaml-designer-unhandled-exception

    Wednesday, January 7, 2015 2:57 PM
  • Looking at this issue http://connect.microsoft.com/VisualStudio/feedback/details/900615/opening-xaml-design-files-fails, it might have the same root cause as the one we're currently discussing.
    Wednesday, January 7, 2015 3:45 PM
  • Hi Nikolami


    Thank you for looking into this issue.


    I checked these 2 paths in regedit and unfortunately I can't see anything related to my software in them. All my apps use BackgroundWorker, but I guess it is different than what the other person did to cause this problem.

    I sent you an e-mail.

    Wednesday, January 7, 2015 4:42 PM
  • @storm_blast

    I only started looking into this a little bit ago. And performed some searches on Google but the search results that appear to describe errors with crashing due to XAML are from a pretty good while back as well as some more recent ones.

    Therefore it's difficult to believe an issue like this may be occuring in newer versions of Visual Studio. But apparently it is.

    I have VS 2012 which I could target .Net 4.5 with and see if the issue occurs with a Windows Store app. Or perhaps WPF would do this also but I don't know. However without having your project then I would not be able to be certain I could get the same result. Also my PC is Windows 7 therefore the issue may not occur especially with regard to Creating Native Images (see below) not automatically running on my system I suppose.

    One solution for an older VS was to dismiss XAML design view by performing the below which I disagree with.

    Right-click on a XAML file in the Solution Explorer

    • Select "Open With..."
    • Select "Source Code (Text) Editor"
    • Click on "Set as Default"
    • Click OK
    • You're done!

    Another solution I believe involves Creating Native Images which says "Starting with the Windows 8 operating system, native images can be created automatically by the .NET Framework or manually by developers or administrators. Native images can only be created manually on earlier versions of Windows.". As the solution is about using Ngen.exe (Native Image Generator) command line using "ngen/delete *" in the command line (without the quotes of course). Although I don't see "delete" as an available option for the ngen command. The article explaining this useage was about VS 2008 though so possibly ngen has been altered since then. Supposedly this would delete a cache. Perhaps emptying the queue may be a better idea since ngen seems to support being able to do that.

    Perhaps disallowing native images to be created would solve the issue or something. Some more info is below.

    Automatic native image creation is available on all Windows Client SKUs starting with Windows 8. An assembly is eligible for automatic native image creation if it meets the following criteria:

    • The assembly targets the .NET Framework 4.5 or later.

    • The assembly is installed in a supported location:

      • The global assembly cache.

      • A Windows Store app package.

    The .NET Framework automatically manages the tracking, creation, and reclamation of these native images. For information about the automatic reclamation of native images, see Reclaiming Native Images.


    La vida loca

    Wednesday, January 7, 2015 6:46 PM
  • I have the exact same issue. Fairly fresh windows install (8.1), about 2 weeks old. Installed vs2013pro using web installer (included update 4 immediately). Resharper 8. Any windows store or phone apps, even empty ones just created from the VS built in templates, have this issue. But Phone8 Silverlight is OK...

    I'm open for a skype session or so to help debug this issue.

    Sunday, January 18, 2015 9:19 PM
  • Hi boekabart - could you please send me email at nikolami at microsoft dot com? I'd like to debug the issue with you.

    Does the issue reproduce if you uninstall/disable Resharper?

    Thursday, January 22, 2015 10:58 PM
  • I also got the similar issue. I'm using VS Community 2013 Update 4.Did anyone succeeded in solving the issue.
    • Edited by Mahindar Wednesday, February 11, 2015 2:52 PM
    Wednesday, February 11, 2015 2:52 PM
  • Nope, not solved. Some more help would be appreciated.

    Monday, March 9, 2015 9:03 AM
  • Same Issue with blank project! I'm no able to go on!!!

    NO SOLUTION YET!???

    Monday, March 30, 2015 3:57 PM
  • Tuesday, March 31, 2015 6:54 AM