Improve the XAML Designer performance
It often takes several seconds for a XAML Window to fully display. The editor is constantly pausing as I type, sometimes for as long as a second, before catching up with keystrokes.
Peter S commented
With my Visual Studio 2012.4, and 2gb of RAM used by XDeskProc, I resolve the problem by turning off the data loading in View Model’s constructor if in design mode. This way you can still have design mode
If DesignerProperties.GetIsInDesignMode(New DependencyObject) Then
‘ Do nothing
‘ Do something
Mettiu2005 . commented
Disabling Fx icon (visible in Design mode) did not help me, but this helped (opening with Source Editor)
Ralph Roza commented
After some really slow performance by the XAML designer, I was able to restore it for my system. It is a pleasure to work with again. See:
That worked fine to me: http://nuxtech.blogspot.com.br/2012/08/visual-studio-silverlight-xaml-designer.html
I can't see the Fx icon!!?!?!?!?!
VS 2102 is the worst Visual Studio ever
In the XAML designer, there is an option called Turn on/off rendering of Effects, the icon is (Fx), when I Turned off that option the XAML designer comes faster like vs2010 again :)
Joberto Diniz commented
The computer memory goes to the sky when I open VS2012 with a WPF project. It's just too slow
Wouter Vos commented
For me it's 10 second hangups when returning to the editor window. This can be from anywhere and does not happen every time, so returning to the xaml editor is always scary :(
Fulltime WPF Developer commented
I am also having serious issues with WPF/Xaml designer. It is almost unusable and very frustrating. Please improve the Xaml designer performance to match the windows form designer performance. Otherwise this great technology will be wasted and nobody will use it.
Yes the editor is way to slow - almost not useable. Why do think there are still simple designers out there to get the job done without waiting for Visual Studio to get ready for input
Guido Kraus commented
5+ seconds on a Core i7 just when switching between tabs isn't acceptable. VS2010's XAML editor really is a pain.
Core i7, 3.4Ghz Quad Core, 12GB Ram, The XAML editor in vNext takes 5-20 seconds to render (you can continue working while it loads message).
On Metro projects, the XAML editor crashes whenever you try to drag a control onto the designer. I followed the command line steps to fix it provided on blendinsider to no avail. The XAML editor is completely unusable for me at this point (no exageration, it flat out doesn't work).
For reference, I was using Visual Basic as the language, but I also tried a c# project.
Sharon Talbot commented
I saw this user voice site yesterday and was happy. Today, after opening up a xaml file for the build and scrolling a bit to get to the section I want to modify, I got the spinning ball of doom that indicates I should wait. I've had to time google bharry, find the post that mentioned this site, login, find this post, and edit and post this comment. Visual Studio is still not responding.
Maximilian Haru Raditya commented
I personally find out that Blend XAML designer/editor is much more *responsive* (yes, it means performance) and better than VS XAML designer/editor. So I think it's better to replace VS one (and deprecate it) with Blend one and thus incorporate all benefits found in Blend.
It doesn't seem making any sense for me given the fact that MS create two different XAML designers/editors. They said they have finite resources, but it seems they are wasting resouces on this one. It's better to create just one for both of them and combines both best features: a hybrid XAML designer/editor.
John John commented
For me it takes sometimes more then 20 seconds to switch to the designer. And when I get back and forth between two tabs, I get a designer freeze of several seconds.
Please fix the performance and the exceptions rendering when blend can render the view.
I have perf watson extension and the status bar indicator installed and see my views taking 5+ seconds to render on a core i7 box.
I see an issue with merged dictionaries coming from another assembly that's not part of the project.