WPF performance and .NET Framework Client Profile related blogs provided by Jossef Goldberg.
Not sure if folks are aware, but Visual Studio 2010 now includes WPF Visualizer. This can really help you during debugging.It basically allows you to explore and visualize the Visual Tree and properties of a WPF object during a debug sessions. Similar to what Mole was doing, but this is now built-in to Visual Studio 2010.
To use: During debug, in a DataTip, Watch window, Autos window, or Locals window, next to a WPF object name, click the arrow adjacent to the magnifying glass icon. See images below for the SDK example I used:
Not sure if folks aware that Snoop for WPF 4.0 has been available for a while. You can download it from here.
This version includes other impressive list of improvements that you can read about here. Thanks to Corry Plotts and others (Dan Hanan, Mark Kharitonov, etc) who improved on Pete Blois’ original Snoop.
The WPFPerf tool comprises of a suite of performance profiling tools that allow you to analyze the run-time behavior of your WPF application and point to potential performance bottlenecks. We finally release the version that also supports .NET Framework 4 (WPF 4).
This version of the tool (WPFPerf 4) will allow you to profile both WPF 3.5 SP1 and WPF 4 based applications. The WPFPerf 4 tool is included with the Windows SDK for Windows 7 and .NET Framework 4 (Windows SDK 7.1). So you are welcome to download and send us your feedback.
By the way, the tool itself will run on machines with only .NET 3.5 SP1 or only .NET 4, if both are present it will use .NET 3.5 SP1. Also, I am not sure how many people had a chance to look at the documentation that is installed with the tool , but we think it is very useful so don't forget to check it out.
Update (6/14/2010): We heard that few folks complain that the Visual Profiler cannot correctly attach to the WPF application in the new WPFPerf for WPF 4. After some research we think this has to do with a bug in our DateTime initialization which cause anyone in a time zone > GMT to not get any data in VisualProfiler (for a few hours at least). Until we post a fix, a temporary workaround is to set your time zone > GMT (e.g.to Eastern or Pacific Standard Time Zones) when you first attach VisualProfiler.
Please try this workaround and let us know.
Update (8/24/2010): A patch to that fixes the bug in Visual Profiler for certain time zones is now available. See here.