My blogging tends to follow certain life cadences and mine has mostly been work, work and well work.Now that I’m prepping for Build 2014 I’ve switched back from information gathering to information sharing which means dusting off my blog.
It feels like some maddening wisdom is embedded here, especially the last sentence. “This article is really dulcet, a friend gave me a look.
I catched sight of, I would like to express the feelings I looked.
There is no shortage of information out there on how to speed up the performance of WPF applications, but too often the focus is on the weird stuff instead of the simpler issues.
I’m not going to talk about things like writing to to optimize drawing—it’s a topic covered to death elsewhere.
Instead, this is meant to be a slightly more practical guide to squeezing performance out of WPF in ways that are probably more likely affecting you.
and its subclasses List Box and List View exacerbate performance problems because these controls are highly dynamic (resolution happens “late”), involve WPF collections (which are slow), and have difficult and unpredictable lifetimes for their child controls.Scrollbar performance is often a big problem in larger WPF apps because of problems that seem trivial for small collections, but suddenly blow up with larger data sets.Also, it can be difficult in WPF to know exactly when the system is finished with an object.For views, you get the get a WPF notification that a viewmodel is about to go unused by a view.Blend-style behaviors also have their own set of lifetime problems.Then there are some problems (like this and this) where WPF leaks for you too.