Book Image

Learn WinUI 3 - Second Edition

By : Alvin Ashcraft
5 (1)
Book Image

Learn WinUI 3 - Second Edition

5 (1)
By: Alvin Ashcraft

Overview of this book

WinUI 3 takes a whole new approach to delivering Windows UI components and controls and has the ability to deliver the same features across multiple versions of Windows. Learn WinUI 3 is a comprehensive introduction to WinUI and Windows apps for anyone who is new to WinUI and XAML applications. This updated second edition begins by helping you get to grips with the latest features in WinUI and shows you how XAML is used in UI development. The next set of chapters will help you set up a new Visual Studio environment, develop a new desktop project, incorporate the Model-View-ViewModel (MVVM) pattern in a WinUI project, and develop unit tests for ViewModel commands. Next, you’ll cover the basics of data access from WinUI projects with a step-by-step approach. As you advance, you’ll discover how to leverage the Fluent Design System to design beautiful WinUI applications. You’ll also explore the contents and capabilities of the Windows Community Toolkit and learn how to create cross-platform apps with markup and code from your project using Uno Platform. The concluding chapters will teach you how to build, debug, and deploy apps to the Microsoft Store. By the end of this book, you’ll have learned how to build WinUI applications from scratch and how to modernize existing desktop apps using WinUI 3 and the Windows App SDK.
Table of Contents (20 chapters)
Free Chapter
Part 1:Introduction to WinUI and Windows Applications
Part 2:Extending WinUI and Modernizing Applications
Part 3:Build and Deploy on Windows and Beyond

Working with events and commands

It’s time to update the project to move the event handling code to MainViewModel. By the end of this section, you will have removed all the code that was added to the MainWindow.xaml.cs file, except for the ViewModel property. This will be great for the separation of concerns, as well as for the maintainability and testability of the project.

We could use the same process of wiring up events with the Add button’s Click event and connect it to a method on the MainViewModel class. There are two problems with this approach:

  • The View and View Model layers become more tightly coupled, reducing maintainability
  • UI concerns are injected into the view model, reducing the testability of the class

Let’s take another route. The MVVM pattern has the concept of Commands to handle events. Instead of adding a handler to the event of our view element, we will bind that event to a property on the view model. The Command properties...