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

Chapter 5, Advanced Controls

  1. ActivityIndicator shows that something is happening, while ProgressBar tells the user what fraction of the task is complete.
  2. The essential difference as far as we are concerned is that events are typically handled in the code-behind, while commands are handled in ViewModel. Handling commands in ViewModel is preferable because it makes creating unit tests easier or possible.
  3. WeakReferenceManager is the primary object used in messaging, allowing ViewModel to send notifications to View or another ViewModel without a reference to that object, thus supporting loose coupling.
  4. Styles allow you to create a uniform appearance across instances of controls, centralizing the properties and providing all the advantages of well-factored code.
  5. One way to refactor styles is to create a base style and then use BasedOn to create derived types, adding or overriding properties as needed.