.NET MAUI and Blazor – Best of both modern technologies for Mobile, Desktop, and Web solutions from a single codebase.
But app development is of two categories: Existing ones and Greenfield development. New features can be part of the latter quite easily as they’re done from scratch but definitely not that easy on the former as existing investments needs to be protected. And changes can be quite expensive as it needs to be thoroughly validated before rolling out to production use.
This is the fourth article in the .NET MAUI – Blazor series and have provided links for the other 3 articles previously published.
This article primarily focuses on the Blazor Hybrid scenarios.
The reason is the potential of Blazor, the modern web UI stack based on Razor SDK and allows to work with C# language constructs which can be used across multiple frameworks with the introduction of BlazorWebView, now officially supported on .NET MAUI, classic Windows desktop application frameworks such as Windows Forms (WinForms) and WPF.
Very happy to announce the availability of the Shared Class Library project template, a library that targets both Xamarin.Forms and .NET MAUI from one single project.
We all know that .NET MAUI is an evolution of Xamarin.Forms targeting .NET 6 (as of this writing), a cross-platform UI stack (native UI) targeting the Android, iOS, macOS, and Windows platforms to complement the .NET toolchain (SDK & Workloads), and a single base class library (BCL).
Developer Thoughts 