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.I'm terribly sorry for not getting this earlier. I have two tabs on a tab control that use the same User Control on each but the difference is the binding.

Dynamic Data Display integrates well with Bing Maps control to show data on a geographic map in latitude/longitude coordinates.

The controls are compatible with most popular development tools like Expression Blend and Visual Studio.

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.

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.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.Dynamic Data Display 2.0 is a set of Silverlight controls for adding interactive visualization of dynamic data to your Silverlight application.It allows to create line graphs, bubble charts, heat maps and other complex 2D plots which are very common in scientific software.Most notably, with this release, Bailey Ling has added a Power Shell scripting tab.