Xamarin.Forms 5 Preview Ships Ahead of .NET 6 Transition to MAUI -- Visual Studio Magazine

Xamarin.Forms 5 Preview Ships Ahead of .NET 6 Transition to MAUI

By David Ramel
09/29/2020

Microsoft shipped a pre-release version of Xamarin.Forms 5 ahead of a planned transition to MAUI, which will take over beginning with the release of .NET 6 in November 2021.

MAUI, unveiled in May, stand for .NET Multi-platform App UI and is the evolution of Xamarin.Forms for creating native cross-platform apps with .NET. It will be used for the development of Android, iOS, macOS and Windows apps.

Xamarin.Forms will continue to be updated until .NET MAUI arrives with .NET 6, after which it will only receive priority servicing for one year.

**[Click on image for larger view.]** MAUI Overview *(source: Microsoft).*

While it's still in the planning and early development stages, Microsoft said the dev team's goals for MAUI include:

Improve app performance
Improve simplicity of control extensibility
Improve simplicity of contributing
Enable developer options to use Model-View-Update (MVU) and Blazor

The differences between Xamarin.Forms and MAUI are illustrated here:

**[Click on image for larger view.]** MAUI Compared to Xamarin.Forms *(source: Microsoft).*

In an FAQ that asks the question "Should I upgrade my Xamarin.Forms applications to .NET MAUI?" Microsoft says: "Initially, we recommend you explore .NET MAUI on new projects. We are working to make the transition from existing projects as seamless as possible as you will enjoy project system improvements, a new .NET, and a new renderer architecture in .NET MAUI."

So, as early previews for MAUI are expected late this year, Xamarin.Forms itself continues to evolve with the pre-release v5.

"Xamarin.Forms 5 brings to stable release features that you have seen in preview over the latest several 4.x releases," Microsoft's David Ortinau, principal program manager, Mobile Developer Tools, said in a Sept. 29 blog post. "This includes solid and gradient Brushes, CarouselView, drag-and-drop, RadioButton, Shapes, and SwipeView. These new features inject new creative potential for your application designs to create beautiful, interactive experiences."

For coverage of those 4.x releases, see:

Ortinau advised developers who are considering updating their apps to Xamarin.Forms 5 to be aware of changes including:

Visual Studio 2019 is the minimum version to use
MasterDetailPage and properties have been renamed
UIWebView has been removed to address Apple restrictions
MediaElement and Expander have been moved to the Xamarin Community Toolkit. C# UI is to follow.
(Preview) DataPages and Theme packages have been removed from the NuGet release

More information is found in the release notes.

Ortinau also pointed to further guidance on the new features and changes:

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.