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...

In the preceding example, the Department property has a data binding with the TextBlock control and thus the associated TextBlock displays the text returned by the property. Similarly, the PersonName property has a data binding with a TextBox control. As the data binding has been made to the Text property of the TextBlock (with TwoWay mode), it automatically updates the associated property when the user changes it in the UI.

So, when you hit the Submit button, the OnSubmit event triggers, and it directly reads the PersonName property instead of fetching the text from the UI by accessing the Text property of the TextBox control.

When you hit the Reset button, the OnReset event triggers and it sets the PersonName property to an empty string. But the UI does not change. This is because the CLR property does not have a notification mechanism to automatically update the UI when a value change happens to it.

To overcome this, WPF uses the INotifyPropertyChanged interface, which...