views:

356

answers:

3

I've worked with Visual Studio 2008 and editing XAML was really painful because the designer reloaded very slowly. Now I have installed Visual Studio 2010 and it seems to me that the XAML editor + Designer haven't changed much.

For example in order to force designer to change a color in my control I have to close the xaml file and open it again.

Is it just my problem?

I've tried this solution: http://stackoverflow.com/questions/859335/visual-studio-2008-xaml-editor-not-working-disappeared but it didn't help.

Are there any better tools for Visual Studio to edit XAML?

Thanks!

EDIT: Compiling forces redrawing of the designer but my solution is quite large now and it takes a lot of time.

+1  A: 

I didn't experience the same problem, instead I saw that Visual Studio 2010 is faster than its previous version to load a XAML into the designer.
Btw, I suggest you to show only the XAML, either collapsing the designer window or pressing ESC during the loading: the first time is slow, but other times is faster.
Hope this helps.

Maurizio Reginelli
+1  A: 

If you can, get hold of Expression. For Visual Studio 2008 it was a much better visual XAML editor.

I know a lot of what it does was incorporated into Visual Studio 2010, so there might not be a lot of difference between the two now.

ChrisF
I've heard about it. Is it possible to integrate it in Visual Studio or it is only a stand-alone application?
MartyIX
@MartyIX - it's a standalone application that opens Visual Studio solution files. It can integrate with source control, you can edit the C#/VB code and you can debug your application from within it to. It's primary function is for designers to be able to edit the XAML without having to have a full version of Visual Studio installed.
ChrisF
Will
+1  A: 

I run 2010 on an old core 2 duo (~1.2ghz) laptop with 4gb of memory and the xaml editor is fine.

If you've got a MASSIVE xaml document you might want to think about breaking it into user controls to simplify the document. Also, think about the machine you're running. If it doesn't have at least 3gb of memory you're going to be fighting with the disk. Memory is cheap, make sure you have as much as possible.

Will
I've core 2 duo 2GHz, 3GB RAM. The process devenv.exe takes 150MB RAM. I think it's not about swapping because it would have eventually finished the work but it's not my case.
MartyIX
@Marty you got a real bad graphics card? What's your windows experience number on it?
Will
I've got an average one. The index is 3.5
MartyIX
@marty sounds like a doable system. Not sure then why you'd be experiencing the issues you describe. I'd update my vidya card drivers, no doubt. Might help to get Process Explorer and look at it occasionally when slowdowns occur. You might have some other things going on that are dragging the system down.
Will