• Screenshots
• Why use it?
• Key features
• Download
• Documentation
• Change log
• Support & forums
• Pricing
• Buy now

Five Reasons to Use the WPF Property Grid

Since the .NET Framework already includes a property grid for Windows Forms, and WPF applications can host Windows Forms controls, why use the Mindscape WPF Property Grid?

1. Using Windows Forms interop incurs some visual limitations and the overhead of loading the large Windows Forms assembly. With the WPF Property Grid, you can use WPF graphical capabilities such as composition and transformation to create distinctive user experiences.
2. The WPF Property Grid can be styled and templated to fit into applications with a customized look and feel. As well as styling the control as a whole, you can also style individual value editors to be consistent with your application's style or with specific usability requirements.
3. The WPF Property Grid is much easier to extend than the Windows Forms grid. Furthermore, it can be extended by hosting applications, so you can easily customize the editing experience for classes that aren't under your control, or on a per-property basis.
4. The WPF Property Grid supports custom entries and multiple objects. It can be used as a general-purpose editor for any set of values you need your users to be able to edit, even if these are in the form of named values rather than a class.
5. The WPF Property Grid uses WPF data binding, ensuring that changes are automatically propagated around to and from other user interface elements without the need for code. The use of data binding also means you can use familiar WPF techniques for validation, error handling user interfaces, and user-defined sorting, grouping and filtering. Property search is built in so users can easily find a single value in a long list.

Still not convinced?

Download a free trial and try for yourself, ask a question in the forum or, contact us directly.