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 XmlnsPrefix attribute defines the prefix name that you suggest using in the XAML, while declaring the module namespace. Though it is optional to use the same prefix name, while using the Visual Studio IntelliSense, it automatically adds it.

When you define the XML namespace as URL format, it has multiple benefits over the traditional representation:

  • If you follow the same structure, it is easy to remember.
  • When you are using custom libraries, you don't have to write the complete namespace and assembly every time in each file. Thus, uses of xmlns:behaviors="clr-namespace:CH05.NamespaceCustomizationLibraryDemo.Behaviors;assembly=CH05.NamespaceCustomizationLibraryDemo" can be reduced to xmlns:behaviors="http://schemas.kunal-chowdhury.com/xaml/behaviors".
  • You can define the prefix, so that you can follow the same convention in all the files while defining the XMLNS attribute.