Yet another blog about WPF, Surface, SL, MVVM, NUI.... - Tag - performance

What ? Dynamic resources creates Memory leaks in WPF 3.5 (SP1) ???

JonathanANTOINE@falsemail.com — Sun, 27 Mar 2011 08:12:00 +0200

Everyone is told to not use DynamicResource during its childhood in WPF-(wonder)land. They are simply evil and they kill the app performance. Sometimes, we fall in the dark side of the force and use them effectively to be sure that the application will follow the trend and suits itself well. This is not as bad as it seems and it is in fact sometimes necessary and wanted.

But today, while I was trying to improve the performance and the memory usage of a WPF application I work on, I discovered that they were also creating memory leaks! I felt betrayed. I was using them and they put a knife in my back while I trusted them to be useful.

In this post we will see how it can happens, and how to solve this (little) issue.

I was not alone in this situation and I found out that there were both a work-around and an hotfix available. Here is the information I gathered. Description of the problem When you create and load a ResourceDictionary, the objects you add inside are actually not created immediately. They are referenced in the form of an instance of an object... Read What ? Dynamic resources creates Memory leaks in WPF 3.5 (SP1) ???

[Performance tips] Use the system shadows instead of your own

JonathanANTOINE@falsemail.com — Tue, 27 Apr 2010 23:52:00 +0200

Today a fast and easy tip about shadows and performance. In a project I have recently made, we've told the designer not to use BitmapEffects because they are performance killer. He so decided to create it's own shadows by duplicating each shape and make them looks like shadows(designer magic, voodoo things, etc...). I was then surprised to see... Read [Performance tips] Use the system shadows instead of your own

Freeze brushes directly in the XAML to improve your application's performances

JonathanANTOINE@falsemail.com — Mon, 12 Apr 2010 22:53:00 +0200

When you read the MSDN guidelines to improve WPF's performances you can find that it's a good idea to freeze Freezable objects. It's a quite easy thing to do via the code but it's quite harder to do it directly in the XAML. In this post we will see how to do so. What are freezable objects One upon a time, the MSDN said : A Freezable is a... Read Freeze brushes directly in the XAML to improve your application's performances