I will concur. Aside from a memory hog, VS2010 performance has been ok on my dev box which has an NVidia Quadro card in it. However, there are still some quirks in the environment that I attribute to WPF bugs. I have frequent redraw issues even after applying SP1. I also noticed that my installation has a whole lot of trouble with datasets and pulling up the designer file. TFS 2010 issues have been the most frustrating thus far though. They are better with SP1, but still exist.
I have frequent redraw issues as well with Quadro cards. Particularly when moving VS between screens (we have dual monitor setups). It sometimes whites out portions of it. Occasionally as well it just goes batshit and goes white and flickers as well. Oh and the performance sucks on low end Quadro cards. We upped them to ATI FireGL and they seem ok now. Still not happy about the situation.
Have you tried disabling the use of hardware acceleration? WPF seems to have some issues with some graphics cards, or more accurately some graphics cards have some buggy hardware acceleration. Another thing I have noticed is that use over remote desktop and on VMs (specifically VMWare) can have quirks, then again I thought I read somewhere that WPF has to use bitmap remoting instead of primimtive remoting because Windows doesn't offer them any way to take advantage of primitive remoting because they aren't Win32 based (except their root visual which is an HWND, but everything else uses DirectX surfaces), which is a great example of Microsoft teams having pissing contests that just hurts users.
Yeah tried that. Didn't make much difference. I think the main issue with the Quadro's was the poor quality of drivers more than anything else. Even the WHQL ones are junk.
VMware - forget it - unusable. All our infrastructure is VMware based and we have to do remote debugging on VM's via RDP. Yuck. I think when RDP is used it falls back to a GDI+ backend as HW accelerated primitives cannot be thrown down an RDP link and then uses tiles (as you state).
This is all down to the fact that RDP came before DWM. If it was the other way around we'd be throwing surfaces down the wire which would be nice.
>> This is all down to the fact that RDP came before DWM. If it was the other way around we'd be throwing surfaces down the wire which would be nice.
The joke here is that on Vista to Vista RDP connections (.NET 3.0), WPF was properly remoted over the wire and rendered on the client machine instead of bitmaps being sent. This was removed in .NET 3.5. (http://www.virtualdub.org/blog/pivot/entry.php?id=216)
