Windows Forms and WPF are proven solid frameworks for creating high-performance Windows desktop client applications.
Blazor, a framework for full-stack web development with C# and Razor.
When these two technologies come together, then it’s certainly a delight for the .NET developers as it paves the way to leverage the skills they’re already familiar with and an option to modernize the existing applications.
.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 need to be protected. Changes can be quite expensive as they need 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.
This article is the second part of this MVVM – Made Easy series. The first part of this article, covering the basics, is linked here.
As seen in the first part, INotifyPropertyChanged (INPC) is the interface that defines the event which raises the notification whenever the value of the property gets changed.