Book Image

Mastering Windows Presentation Foundation - Second Edition

By : Sheridan Yuen
Book Image

Mastering Windows Presentation Foundation - Second Edition

By: Sheridan Yuen

Overview of this book

Microsoft Windows Presentation Foundation (WPF) provides a rich set of libraries and APIs for developers to create engaging user experiences. This book features a wide range of examples, from simple to complex, to demonstrate how to develop enterprise-grade applications with WPF. This updated second edition of Mastering Windows Presentation Foundation starts by introducing the benefits of using the Model-View-View Model (MVVM) software architectural pattern with WPF, then moves on, to explain how best to debug our WPF applications. It explores application architecture, and we learn how to build the foundation layer of our applications. It then demonstrates data binding in detail, and examines the various built-in WPF controls and a variety of ways in which we can customize them to suit our requirements. We then investigate how to create custom controls, for when the built-in functionality in WPF cannot be adapted for our needs. The latter half of the book deals with polishing our applications, using practical animations, stunning visuals and responsive data validation. It then moves on, to look at improving application performance, and ends with tutorials on several methods of deploying our applications.
Table of Contents (15 chapters)

Using validation rules – to do or not to do?

In WPF, there are two different approaches for dealing with data validation. On the one hand, we have the UI-based ValidationRule classes, the Validation.Error Attached Event, and the Binding.NotifyOnValidationError and UpdateSourceExceptionFilter properties, and on the other, we have two code-based validation interfaces.

While the ValidationRule classes and their related validation approach work perfectly well, they are specified in the XAML, and as such, are tied to the UI. Furthermore, when using the ValidationRule classes, we are effectively separating the validation logic from the data Models that they are validating and storing it in a completely different assembly.

When developing a WPF application using the MVVM methodology, we work with data, rather than UI elements and so, we tend to shy away from using the ValidationRule classes and their related validation strategy directly.

Additionally, the NotifyOnValidationError and UpdateSourceExceptionFilter...