views:

406

answers:

7

When working in VS2008 (C#) does VS2008 silently crash for anybody when working with WPF? If I touch the XAML it is most likely to crash. I can come back in, clean, then build, then run and it work until I have to touch the XAML again. Then start over again.

It is a solution with about 12 projects in it.

Thanks, jeff

A: 

I and some other people at my company have had a lot of problems when editing a resource dictionary and while a XAML window that uses that resource dictionary is open. Moral of the story, close all XAML windows if you're going to edit a resource dictionary.

Bryan Anderson
There seems to be some correlation with the resource dictionary and xaml. But I have tried closing all XAML windows before working on a resource dictionary. At this point, I am looking to edit xaml and resource dictionaries outside of Vs2008.
jeff
+1  A: 

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=375594

Workaround:

Found real workaround at http://www.dotnet6.com/blogs/wesley_walraeve/archive/2008/10/22/visual-studio-2008-sp1-crashes-toolbox-gt-choose-items.aspx, which was removing TFS Power Commands 2008. Other people have had to remove other things.

Tom
Not quite it. I've disabled my add-ins with the same problem. I might try and remove them next.
jeff
PowerCommands, in particular, causes crashes like this. I used to get consistent crashing on rendering a WPF Window in design mode. When I removed PowerCommands, the crashes went away. REMOVE, don't just disable.
Kyralessa
+1  A: 

SP1 solves a bit of the crashes, but indeed it crashes a lot. Especially when you mix and match winforms + WPF. The crashes alone were a reason to stick with winforms for a while for us ...

Frans Bouma
A: 

We suffer the same problems... I noticed that resharper makes things worse for the WPF editor from time to time...

Ah well.. a daily VS crash keeps the doctor away ?

Arcturus
A: 

VS crashes at my computer very often: several times per day when I work with WPF. But usually it stops responding and I don't remember it to crash silently.

Kaagle
A: 

I know, it's not nice, but simply cleaning the solution works for me. At least until the next restart of VS, but until then you shouldn't get any crashes.

Hades32
+1  A: 

I found the problem to be with the AnkhSvn plug-in. I went to a nightlybuild and it is working good now. Anything above 2.0.6110.379.

jeff