how many VS2010-deadlocks per hour are normal?

Update,

I have the
"feeling" that R# is often the cause/trigger for this, but I don't have any
concrete signs for that.

Now I had a concrete case in my project where each time I tried to paste
something from the clipboard into an existing xaml line containing
"" into the x:Key parameter
VS2010 freezed -- every single time I tried.
After suspending R# it just worked.

--
/\/\arkus.

FWIW, my vs2008 (team system) also freezes when I work with wpf/xaml. I can't work with it at all, just a matter of minutes before vstudio freezes and I have to kill the process.

When I suspend Resharper it works fine.

I don't necessarly have many *per hour*, but there do seem to be problems with XAML intellisense and Resharper.

For me the problems range from:

* Overlapping intellisense popups
through
* Stuttering and laggy performance (on a very high-end machine)
through
* Complete freeze-ups requiring VS to be killed.

I also completely gave up on trying to do WPF development on a 32-bit OS - if you on 32-bit Windows you might be running into virtual memory problems too.

Will

Hello,

FWIW, my vs2008 (team system) also freezes when I work with wpf/xaml. I can't work with it at all, just a matter of minutes before vstudio freezes and I have to kill the process.

I just noticed early this day (before jetbrains.net was unavailable for
hours) that there was a final 5.1 but the final 5.1 is even worse than the
last nightly build, nearly every xaml writing ends in deadlocks -- sure,
suspending R# works, but:
1. that's not fun
2. after resuming all ignored solution wide errors (which don't exist in
5.0) are no longer ignored.

--
/\/\arkus.

Hello Markus,

Presumably, we've fixed this problem. We will publish further info when the
fix will be available. Thank you!

Andrey Serebryansky
Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello,

>> FWIW, my vs2008 (team system) also freezes when I work with wpf/xaml.
>> I can't work with it at all, just a matter of minutes before vstudio
>> freezes and I have to kill the process.
>>

I just noticed early this day (before jetbrains.net was unavailable
for
hours) that there was a final 5.1 but the final 5.1 is even worse than
the
last nightly build, nearly every xaml writing ends in deadlocks --
sure,
suspending R# works, but:
1. that's not fun
2. after resuming all ignored solution wide errors (which don't exist
in
5.0) are no longer ignored.

Andrew,

Presumably, we've fixed this problem. We will publish further info when the
fix will be available. Thank you!

Can't await it :)

--
/\/\arkus.

Markus,

Did you try the latest nightly? Is this still reproduced in your environment?
Thank you!

--
Kirill Falk
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"