Pablo posted a great article over on his blog describing what a hardware-accelerated WPF means to your app. There's also a interesting overview of the various places you can hook into the WPF stack.

Over in the forums a handful of folks have pointed out that profiling WPF is less than seemless, and can be super-frustrating. Even with profiles in-hand, sometimes there isn't a bunch non-WPFers can do without some guidance. One of my personal goals...

Toward the end of my next-to-last post I suggested using the command-line to control profiling. I've been experimenting with this functionality and wanted to post what I've learned. First, IanWho’s blog is a pretty amazing source of VSTS Profiler info...

I'm working on an article for next week where I walk through a WPF performance profile using Visual Studio 2005. The problem is, I don't have anything to profile! Sure I can make something up myself, but I'd much rather walk through something sent in...