Book Image

Windows Presentation Foundation Development Cookbook

Book Image

Windows Presentation Foundation Development Cookbook

Overview of this book

Windows Presentation Foundation (WPF) is Microsoft's development tool for building rich Windows client user experiences that incorporate UIs, media, and documents. With the updates in .NET 4.7, Visual Studio 2017, C# 7, and .NET Standard 2.0, WPF has taken giant strides and is now easier than ever for developers to use. If you want to get an in-depth view of WPF mechanics and capabilities, then this book is for you. The book begins by teaching you about the fundamentals of WPF and then quickly shows you the standard controls and the layout options. It teaches you about data bindings and how to utilize resources and the MVVM pattern to maintain a clean and reusable structure in your code. After this, you will explore the animation capabilities of WPF and see how they integrate with other mechanisms. Towards the end of the book, you will learn about WCF services and explore WPF's support for debugging and asynchronous operations. By the end of the book, you will have a deep understanding of WPF and will know how to build resilient applications.
Table of Contents (13 chapters)
2
Using WPF Standard Controls

How it works...

The PropertyGrid control, part of the .NET Framework, allows you to browse, view, and edit the properties of one or more objects. It uses reflection to retrieve and display properties of any object or type.

Reflection is a technology that allows you to retrieve the type information at runtime.

If you are using WinForm, you will be able to use the PropertyGrid control easily from the control toolbar. But, unfortunately, this control is not available in WPF. To use this inside a WPF application, you will need to use the interoperability of WPF and WinForm. For this to work, we need to use the WindowsFormsHost class.

The WindowsFormsHost class allows you to host a Windows Forms control on a WPF page. It is part of the System.Windows.Forms.Integration namespace and it is available inside the WindowsFormsIntegration.dll assembly. That's the reason why we had to reference the System.Windows.Forms and WindowsFormsIntegration assemblies inside the project.

The default location...