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

Deploying applications with Windows Package Manager

Windows Package Manager, also referred to by its command name WinGet, is an open source command-line package management tool from Microsoft. In this section, we will cover how to use the WinGet command to install published packages and the steps to add your own MSIX packages to the Windows Package Manager community repository, which can be found here: This is where WinGet finds available packages to install. The Microsoft Store is one of the package sources available to WinGet. So, if you plan to publish your application to the store, it is not necessary to also publish it to the WinGet repository.

Let’s start by reviewing the steps to add a package to the community repository.

Adding a package to the community repository

To make your applications available to Windows users with the WinGet command, they must be published to Microsoft’s Package Manager community repository...