Book Image

.NET MAUI Cross-Platform Application Development - Second Edition

By : Roger Ye
3 (1)
Book Image

.NET MAUI Cross-Platform Application Development - Second Edition

3 (1)
By: Roger Ye

Overview of this book

An evolution of Xamarin.Forms, .NET MAUI is a cross-platform framework for creating native mobile and desktop apps with C# and XAML. Using .NET MAUI, you can develop apps that’ll run on Android, iOS, macOS, and Windows from a single shared codebase. In this revised edition of .NET MAUI Cross-Platform Application Development you will be introduced to .NET 8 and get up to speed with app development in no time. The book begins by showing you how to develop a cross-platform application using .NET MAUI, including guidance for migrating from Xamarin.Forms. You’ll gain all the knowledge needed to create a cross-platform application for Android, iOS, macOS, and Windows following an example project step by step. As you advance, you’ll integrate the latest frontend technology into your app using Blazor components, including the new Blazor Bindings feature. After this, you’ll learn how to test and deploy your apps. With new coverage on creating mock .NET MAUI components, you can develop unit tests for your application. You will additionally learn how to perform Razor component testing using bUnit. By the end of this book, you’ll have learned how to develop your own cross-platform applications using .NET MAUI.
Table of Contents (18 chapters)
Free Chapter
1
Part 1: Exploring .NET MAUI
9
Part 2: Implementing .NET MAUI Blazor
13
Part 3: Testing and Deployment
16
Other Books You May Enjoy
17
Index

Understanding client-side routing

The routing and layout of Blazor bear similarities to the concepts of Shell and navigation in the XAML realm. In Chapter 5, Navigation Using .NET MAUI Shell and NavigationPage, we introduced navigation and Shell while discussing the routing strategy of Shell. Shell offers a URI-based navigation experience that relies on routes to navigate to designated pages. The routing of Blazor closely resembles this approach.

Blazor routing allows for seamless transitions between Razor pages. Rendering Razor pages in BlazorWebView is akin to web apps operating in a browser.

In traditional web applications, loading an HTML page in a browser fetches the page from the web server. Selecting a different route subsequently retrieves a new page from the server. However, the process varies slightly for single-page applications (SPAs).

Blazor WebAssembly applications fall under the category of SPAs. When launching an app, it is loaded into the browser, and...