We spoke with Graham Knight about his WPF Table View project. WPF Table View is a lightweight data grid designed to handle very large data sets with 100,000+ rows.
The DependencyProperty and DependencyObject which form the building blocks for most XAML features come with a performance cost. An MSDN article “Optimizing C# for XAML Platforms” discusses this in detail along with ways to minimize its impact.
.NET 4.5 brings with it a generic version of WeakEventManager for WPF developers. In addition to not needing the event-specific subclass, this version also dispenses with the need for listener interfaces.
WPF 4.5 has improved its support for multi-threaded data binding, but the technique is still risky. This report attempts to explain how it works and what’s involved in using it safely.
The Bing Maps Windows Presentation Foundation Control introduces mapping capabilities to WPF via a native control. It includes support for Microsoft Surface, bringing touch features to Bing Maps.
Though it isn’t in the spotlight any more, WPF still continues to be a key-stone for rich client development on Windows. With full access to the .NET libraries and the underlying operating system, no other HTML or .NET-based UI technology can match it. Recognizing its importance, Microsoft is continuing to invest in improving WPF and especially its binding capabilities.
The Extended WPF Toolkit is a compilation of Windows Presentation Foundation (WPF) controls, utilities, and components not included in the standard WPF Toolkit. The new version 1.5 has six new controls in addition to some control updates and bug fixes.
There are many ways to handle design-time data in view-models. While some people use complex dependency injection frameworks or inversion of control containers, the simplest method is to just check the DesignerProperties.IsInDesignTool flag. Unfortunately this has the side effect of embedding the design-time data into one’s application. Jeremy Likness offers a couple ways of working around this.
With Microsoft Surface SDK 2.0 one can write applications for both Surface and Windows Touch devices.
With all the focus on Silverlight, and more recently HTML 5, a lot of people have been wondering about the future of WPF. This in quite understandable, as silence from Microsoft’s press machine often means that the project is on hold, possibly forever. However, it could also mean they aren’t ready to reveal what they are working on.
Silverlight on the browser is better than ever. It is getting the same kind of performance improvements seen with HTML 5 while still benefiting from statically typed languages and JIT compilation. So why is Microsoft barely willing to talk about it at MIX?
Miguel de Icaza, founder of the Mono project, says that support for Windows Presentation Foundation on Mono is possible, but would require funding for 15 to 20 developers over a period of two to three years. As an alternative he proposes using other toolkits, but they too need community support.
When DevExpress released their roadmap for 2011, WinForms barely got a mention. As a ten year old technology that is basically abandoned by its creator this isn’t too surprising. But what it interesting the amount of negative feedback that generated. A lot of DevExpress’s customers just don’t see WPF or Silverlight as a viable replacement for their major applications.