Essential WPF

Session - Advanced WPF Application Performance Tuning and Analysis

In this great WPF performance session, Bart De Smet and Eric Harding have talked about WPF performance and demonstrates some of the performance tools the WPF team uses. One of the important things to do regards performance is to start measure early. Perceived performance, make it feel fast, turn it to an art and not a science. There would be trade offs – CPU versus memory, etc. Memory New WPF application called FishBowl has been announced. It’s a small application dealing with facebook as a case...

UI Virtualization vs. Data Virtualization (Part 2)

Introduction In part 1 I’ve talked about the UI Virtualization concept in WPF, and explained how it is differs from Data Virtualization concept. In this post I would like to share with you a unique solution for Data Virtualization implementation in WPF. Recall from the previous post, Data Virtualization implementation raises several problems, and there is no out-of-the-box solution for Data Virtualization in WPF. First problem: How do we fake scrollbars, so the user will think that it has all the...

WPF Performance Sweets – ContentControl (Part 2)

Part 1 Yesterday I went back to my customer, tried to figure out if the whole concept of using data as the content of a ContentControl instead of holding a logical tree, is truly contribute to the whole system, and guess what? It is not! Well it figured out that setting the content property with non-visual element only postponed the tree-traversal. We figured this out by trying to measure the total elapsed time between setting the content property to null and up until the view completely disappeared...

WPF Performance Sweets – ContentControl.Content = null

Part 2 Background Yesterday I came back from my customers’ place. He had performance issues with his WPF composite application. Each time he navigates away from a page, he pays about 1400ms! – Playing around we’d found that each time a page was changed, the composite framework he uses replaces the old page with the new page by simply updating the ContentControl.Content (placeholder) with the new page. This operation solely took about 800ms! placeholder.Content = newPage; In this post I would like...