CLR Profiler for .NET Framework 4 is now available

David Bronman just posted a new version of the CLR Profiler that now also supports .NET Framework 4 as well as Silverlight 4.  Key Features: Allows you to profile managed memory that uses .NET 2.0, 3.0, 3.5, or 4.  (However, you must always have .NET 4.0 installed on your box in order to use CLRProfiler…


Memory Leak Hotfixes for WPF 4

In the Memory Leak Hotfixes for WPF 3.5 SP1 blog post I mentioned that the memory leak fixes that went into KB981107 were only available for WPF 3.5 SP1. I am now happy to announce that these memory leak fixes are also available for WPF 4.  You can get the fixes for WPF 4 from…


New Silverlight Performance Blog

Wanted folks know that we have started a new Blog that is dedicated to Silverlight performance. We have uploaded two posts: Silverlight Startup Best Practices Analyzing Silverlight Memory Usage: Part 1 – Obtaining Measurements We plan to add additional posts in the near future, so please stay tune.


TimeZone patch to WPF Performance Profiling Tools for WPF 4 is now available

In the WPFPerf Performance Profiling Tools for WPF 4 is now available! post, I mentioned that a bug caused the Visual Profiler to not display any data in certain time zones. A patch is now available to fix this issue. To install the patch: Install the WPF Performance Tool like you normally would by installing…


Software Rendering Usage in WPF

As you know by default WPF uses Hardware acceleration (GPU) to render its content (aka Hardware rendering). In most cases rendering using Hardware (HW) acceleration is much more performant than rendering using Software. In some small cases SW rendering may be faster (E.g. low end graphics card sometimes found in Netbooks). WPF will always attempt…


Memory Leak Hotfixes for WPF 3.5 SP1

Hopefully folks saw my related blog post Finding Memory Leaks in WPF-based applications .In this post below I wanted folks to be aware that we released few other KB Articles (Hotfix) that address other various memory leaks reported in .NET 3.5 SP1. Some of these fixes made it to .NET 4. 1. KB981107 (See:…


WPF “Airspace” when using WEB Browser control

As you may know, when you interoperate WPF with other technologies you can’t overlay WPF and WinForms/Win32 content because of the “airspace” limitations (read more here).Any given pixel in a window is either owned by WPF or WinForms/Win32, not both. On the other hand, you can overlay all the WPF content you want because WPF manages and…


WPF Visualizer in Visual Studio 2010

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…


Snoop for WPF 4

 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.


WPFPerf Performance Profiling Tools for WPF 4 is now available!

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…