Book Image

.NET MAUI for C# Developers

By : Jesse Liberty, Rodrigo Juarez
3.7 (6)
Book Image

.NET MAUI for C# Developers

3.7 (6)
By: Jesse Liberty, Rodrigo Juarez

Overview of this book

While UI plays a pivotal role in retaining users in a highly competitive landscape, maintaining the same UI can be tricky if you use different languages for different platforms, leading to mismatches and un-synced pages. In this book, you'll see how .NET MAUI allows you to create a real-world application that will run natively on different platforms. By building on your C# experience, you’ll further learn to create beautiful and engaging UI using XAML, architect a solid app, and discover best practices for this Microsoft platform. The book starts with the fundamentals and quickly moves on to intermediate and advanced topics on laying out your pages, navigating between them, and adding controls to gather and display data. You’ll explore the key architectural pattern of Model-View-ViewModel: and ways to leverage it. You’ll also use xUnit and NSubstitute to create robust and reliable code. By the end of this book, you’ll be well-equipped to leverage .NET MAUI and create an API for your app to interact with a web frontend to the backend data using C#.
Table of Contents (18 chapters)
Part 1 – Getting Started
Part 2 – Intermediate Topics
Part 3 – Advanced Topics

Displaying collections

It is common to have a collection of data and to want to display it in a list, allowing the user to select one or more items and then do some work with those items. There are a couple of ways to do this in .NET MAUI, but the most common (and best) is to use CollectionView.

To see this at work, examine Preferences.xaml along with its code-behind Preferences.xaml.cs and ViewModel, PreferencesViewModel.cs. We will use this page extensively as we build Forget Me Not, but let’s start slowly.

Our goal is to create a list of the user’s preferences (shirt size, music genre, and so on). For that, we’ll use CollectionView, and we’ll, of course, need a collection to view. The page, when completed, will look much like this:

Figure 5.4 – The Preferences page

Rather than each line being a unique object, we’ll create one type that we can show repeatedly. In the Model folder, create a Preference class: