Announcing .NET MAUI Preview 5

David Ortinau

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:

Image mauiFadeTo


There are a few ways to perform animation in .NET MAUI, the easiest of which is using view extension methods such as FadeTo, RotateTo, ScaleTo, TranslateTo, and more. In the following example I grab a reference to each view bound to the layout (see bindable layouts) using the new HandlerAttached event:

<DataTemplate x:Key="FavouriteTemplate">
    BindableLayout.ItemTemplate="{StaticResource FavouriteTemplate}"
    BindableLayout.ItemsSource="{Binding Favorites}"

When the page appears I then animate the views in with a slight stagger to create the beautiful cascade effect.

public partial class FavoritesPage : ContentPage
    List<Frame> tiles = new List<Frame>();

    void OnAttached(object sender, EventArgs e)

        Frame f = (Frame)sender;

    protected override async void OnAppearing()

        await Task.Delay(300);

    async void TransitionIn()
        foreach (var item in tiles)
            item.FadeTo(1, 800);
            await Task.Delay(50);

For more complete orchestration of view animations, check out the Custom Animation documentation which demonstrates adding multiple child animations that can run parallel.

You can view and run the source for this example from the WeatherTwentyOne project on GitHub.

UI Components

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.

Image maui pre5 controls

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(
        new AppShell()

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.

<Shell xmlns="" 

    <FlyoutItem Title="Margin and Padding">
        <ShellContent Route="marginpadding" 
                      ContentTemplate="{DataTemplate pages:ControlsPage}" />

    <FlyoutItem Title="ActivityIndicator">
        <ShellContent Route="activityindicator" 
                      ContentTemplate="{DataTemplate pages:ActivityIndicatorPage}" />



Image maui shell catalyst

Get the very latest information about controls, layouts, and features on our .NET MAUI status page.

Single Project Templates Updates

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.

visual studio showing two projects

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.

Getting Started with .NET MAUI Preview 5

In this release we’ve enabled restoring your project without adding a custom NuGet source. Just create a new project and run it! To get all the latest pieces, we continue to recommend running the maui-check dotnet tool.

To install:

$ dotnet tool install -g

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.

$ maui-check

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!

Note: If you installed .NET 6 Preview 4 previously (either directly or by installing .NET MAUI), then you may run into issues installing and running .NET 6 Preview 5. See the .NET 6 Known Issues for instructions on how to fix up your installation.

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. Be sure to disable XAML Hot Reload to avoid a type error, or stick with Visual Studio 2019 version 16.11 Preview 2.

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.

Feedback Welcome

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.


Discussion is closed. Login to edit/delete existing comments.

  • Nicolò Carandini 0

    On the WinUI side, with Visual studio Version 16.11.0 Preview 2.0, I’ve successfully run the app created by the template, but I’ve noticed three strange things and I’m curious to know if it happens “only on my PC”:
    1) On the WinUI project the Dependencies node in the Solution Explorer shows a warning sign of missing SDK but I’ve double checked and the SDK is installed. Moreover, the projects builds and the app run fine.
    2) When the app starts, the window has only the background color and nothing else is shown. The text, the “click me” button and the image are shown only when I resize the window.
    3) When I click on the “click me” button, the layout of the page changes showing a wider margin.

    • Rod Macdonald 0

      I was pursuing a Blazor MAUI app using the ‘out of the box’ template which has similar behaviour to what you mention:
      1) missing SDK which I definitely wasted cycles on, gave up trying to fix but the WinUI project ran regardless;
      2) solid indigo background – no Blazor app gets loaded (the usual counter/weather code is within the solution files but it doesn’t load) which is a bit frustrating;
      3) no pretty picture on re-size but if the Blazor code loaded I’d be happy!;
      4) there’s no 3rd project as per preview 4 (which incidentally rendered the same indigo screen and caused manifest issues when I upgraded to preview 5 and VS P2);
      5) haven’t observed the margin resize issue though haven’t specifically looked into that.

  • Charles Roddie 0

    David you mentioned that in this preview you hoped to be able to say whether the performance goals of MAUI vs Xamarin.Forms were being met. Is that the case yet?

    This blog post worries me a little because the Xamarin Org was always adding features, without removing or fixing old features, and that’s why Forms became unmaintainable. Hence the need to start over with MAUI. But if you are going to bring all the same things over then what is the point? Are handlers by themselves enough to give all the benefits promised? The features mentioned here (Animations, Shell, single project) are inessential compared with making the base controls work reliably and performantly and without platform discrepancies.

  • Peter Drier 0

    Maui sounds promising. A problem I’ve had with all .net Core though is distribution of a plugin based WPF application.

    In 4.7.2, I can zip each plugin project’s output, and unzip the appropriate plugins based on user entitlements in their install directory. (I have an installer/distribution process already)

    Trying to do this in core 3.1 or 5, I’ve had loads of troubles. Seems that the optimizations to slim down build/publish output don’t understand the concept of plugins. It’s honestly held up my migration for a year+ now.

    Ideally I’d be able to build the “Core” app which is the shell and required bits to get running. And then each plugin would be zipped containing just the incremental files needed for that plugin vs. what’s already in Core. The 4.7.2 version I have now works, but the plugin zips contain much of the “Core” binaries as well, bloating their distribution.

    If it’s not too late, maybe the build process could still get some love in Maui covering this case?

  • jia liang 0

    Hi David.

    you are doing great job.

    please IGNORE some one who wants a lot like WASM AOT JIT and think it not as good as flutter. I see there is one who wants linux and so on.

    Ignore them and keep going.

    they only wants to ASK。only to disappointed.

    • Jason Rosenthal 0

      We have a fair amount of Silverlight to port over as it is going out of support soon. If not WASM what do you suggest for minimal time and cost?

  • Nuri YILMAZ 0

    Every day I watch a new fall story and news. Happy news -preview anounces- comes one after another, but for some reason we are not happy.

    Can anyone actually run “Hello World” with MAUI? Install 5 no no no install preview 6.11 no VS 2022 but check maui. Maui should be there! Terrible.

    • jia liang 0

      just for this you are not happy? please keep happy.
      if you are not happy you can eat hamburger and coke

  • jack esque 0

    Hi I´m new so I have some question Can I use mvu style for desing all my projects in C# and then have ability that my code work with mac, ios, android and windows when I use vs code instead of vs community? there any source where can I check some projects write in MVU with c# for windows? when will it arrive this new mvu pattern to the previews version of maui?


  • Enrique Ledesma 0

    How do you access mobile devices, such as the camera, from .NET MAUI?.

  • Asad Mehmood 0

    Hi David, thank you for all of the good stuff. I am interested to know if you people have plans to improve startup time on Android? or is it going to be few percent gain as compared to Xamarin forms that comes with dotnet core? any radical improvements expected? this is really a show stopper for consumer Apps.

  • Meriton Bytyqi 0

    I am having trouble with deploying the application on an Android Emulator. About 5 seconds after deploying the application on the emulator, it crashes.

    “[] * Assertion at /__w/1/s/src/mono/mono/mini/debugger-engine.c:1088, condition `found_sp’ not met
    [libc] Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 10594 (.NET ThreadPool), pid 10509 (eatherTwentyOne)”

    How do I solve this?

  • Linh Le 0

    How does MAUI Blazor App load javascript? I tried to build MAUI Blazor App with some javascript libraries but it didn’t work

Feedback usabilla icon