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


Styles allow you to provide a uniform look to your controls by putting all the details in one place.

You create a style for a control type (for example, Button), and that style is applied to all controls of that type (refer to the Explicit versus implicit styles section). You can also base a style on an existing style, extending or modifying the original.

Styles can be stored on the page that uses the control, or they can be stored at the application level. In either case, they are created inside ResourceDictionary, typically declared at the top of the file. To make them available at the application level, just put them in App.xaml.

Where to put your styles

If you are only going to use the styles on objects on a single page, it makes sense to put the styles in the resources of that page. If you want to be able to reuse these styles on multiple pages, then you will want them in App.xaml.

As an example, let’s return to the Login page and create ResourceDictionary...