While we are still recovering from Microsoft Build and .NET 6 Preview 4, we are here to share our continued progress with .NET Multi-platform App UI (.NET MAUI) with .NET 6 Preview 5. In this release we have enabled animations and view transformations, completed the porting of several UI components, and introduced improvements to the single project templates.
We have also published our first batch of preview documentation covering introductory and foundational aspects of .NET MAUI: https://docs.microsoft.com/dotnet/maui/.
In this release several controls now have all properties and events ported to handlers from the renderer architecture of Xamarin.Forms, including ActivityIndicator, CheckBox, Image, and Stepper. In previous previews you would need to check if a control was ported and register renderers from the compatibility package for those unavailable. In .NET MAUI Preview 5 we have made this much easier by updating the UseMauiApp extension (see the Startup wiki) to wire up all the controls for you, whether they are based on handlers or renderers.
Also new in preview 5 is the first introduction of Shell, an application container that provides URI navigation and a quick way to implement flyout menus and tabs. To get started add Shell as the root element to your window in the App.xaml.cs. The typical pattern I follow is naming it "AppShell", though you can name it as you wish.
protected override IWindow CreateWindow(IActivationState activationState)
return new Microsoft.Maui.Controls.Window(
Now in your AppShell class start populating the menu with content using the type that represents the navigation you wish to display, either FlyoutItem or Tab. These are not UI controls, but rather represent the types that will create those UI controls. You can later style the controls with content templates which we'll introduce in preview 6.
We have made progress in this release consolidating the multiple WinUI projects into one. Now when you dotnet new maui a project you'll see two projects: the multi-targeted .NET MAUI project, and the WinUI project.
Now to run the WinUI project you'll have no confusion about which project to choose. This is one step closer to the final vision of having just one project that can build and deploy to all supported platforms. In order to support this, you'll need to install these Project Reunion 0.8 (Preview) extensions for Visual Studio 16.11 Preview 2.
In this release we've removed the need to add custom NuGet sources to your projects, so now you can create a new project and run it! To get all the latest pieces, we continue to recommend running the maui-check dotnet tool.
$ dotnet tool install -g redth.net.maui.check
Now run and follow the updates to get .NET 6 Preview 5, platform SDKs, .NET MAUI, project templates, and even check your environment for 3rd party dependencies.
If you wish to go step-by-step yourself, you can install everything individually with these instructions.
Once installed, you're ready to create a new app based on the preview 5 template.
$ dotnet new maui -n MauiFive
Open your new MauiFive.sln in Visual Studio 16.11 Preview 1 and run the platform of your choice!
Eager to try Visual Studio 2022 Preview 1? Start exploring with the mobile platforms using the Android emulator and iOS with a remote iOS device, or connected Mac host. In the future, Project Reunion extensions will support Visual Studio 2022 and you'll be able to use all the platforms on Windows.
If you have existing .NET MAUI projects you wish to migrate to Preview 5, I recommend creating a new project like above and copying your files over to the multi-targeted project so you can avoid the trouble of reconciling the WinUI projects.
For additional information about getting started with .NET MAUI, refer to our new documentation website.
Please let us know about your experiences using .NET MAUI Preview 5 to create new applications by engaging with us on GitHub at dotnet/maui.
For a look at what is coming in future releases, visit our product roadmap.