Improve WPF Editor performance
Improve Visual Studio WPF Editor performance. With Visual Studio 2010 it is very good, but also a bit slow.
Mira Hedl commented
@Maximilian Very true. It indeed does not make any sence to have twro different designers/editors.
You'll be pleased that in Visual Studio 11 it'll be exactly like that. "VS Designer" will be replaced with Blend one.
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.
Ivan Novitskii commented
Use xml editor for xaml!
This suggestion should be moved to the VS Performance Forum (http://visualstudio.uservoice.com/forums/131389-visual-studio-performance) or just marked as ACCEPTED so that the votes are returned.
Hey folks, you may have noticed, but based on all the feedback about improving performance, we have opened a UserVoice forum (look in the right-hand pane for Visual Studio Performance) to let folks vote on what areas they would like to see improved. This is very helpful to us, since performance is such a broad topic. Take a look and cast your votes, to help us prioritize areas that matter the most to you.
Doug Turnure - Visual Studio PM
Joanna Mason, it seems you misunderstood this entirely. This idea does NOT say "Incorporate Blend features". It says "Improve WPF Editor performance"
Joanna Mason commented
Thanks for the feedback on wanting Blend features incorporated into Visual Studio. This is something we have heard from many customers and we're considering it, stay tuned!
Expression Blend PM
@Winston - totally agree. In my dev shop, the developer is the designer, so having two products makes no sense. Include the Blend design features with VS, or make Blend available with the MSDN Pro subscription.
also fix the issues with blend being able to display the view while vs2010 cant due to exceptions and vice versa.
One great way to help the Visual Studio team out here is to install Perf Watson. This is an extension to Visual Studio which monitors and reports on performance problems in the product including the editor. This is an invaluable tool to help the team find and fix real world performance problems.
Winston Pang commented
I second that, why not merge the blend editor into VS, have one unified editor, not different ones on two products.