Maui Toolkit Appearing and Disappearing commands not triggering after upgrading from .NET8 to .NET10

Question

Maui Toolkit Appearing and Disappearing commands not triggering after upgrading from .NET8 to .NET10

Peter Stuart 0

I have a MAUI app written in XAML and C# that I have recently upgraded from .NET8 to .NET10. I had a lot of functionality change which I was able to fix but I have noticed that my Appearing and Disappearing commands have stopped working which has destroyed a lot of my app's functionality. I have written the app using MVVM and I intend to keep it that way, rather than hacking around the view to get my Appearing and Disappearing code to work again.

In my login page I used to have this in the View:

    <ContentPage.Behaviors>
        <toolkit:EventToCommandBehavior EventName="Appearing" Command="{Binding AppearingCommand}"/>
    </ContentPage.Behaviors>

And this in the ViewModel:

        public DeviceLoginViewModel(ICaptureApi cApi) {
            LoginCommand = new AsyncRelayCommand(Login, ValidateLogin);
            AppearingCommand = new AsyncRelayCommand(OnAppearing);
            PropertyChanged += (_, __) => MainThread.BeginInvokeOnMainThread(LoginCommand.NotifyCanExecuteChanged);
            AutoBusy = false;
            _cApi = cApi;
        }


        public ICommand AppearingCommand { get; }

        async Task OnAppearing() {
            CaptureApiKey = Settings.CaptureApiKey;

            if (CaptureApiKey.Trim().Length != 0) {
                await LoginCommand.ExecuteAsync(null);
            }
            else {
                ShowForm = true;
            }
        }

This used to have it so that when the user opens the app, the app logs in automatically. However, after updating to the latest .NET version, this does not work anymore.

I have tried updating the XAML in the view to this:

    <ContentPage.Behaviors>
        <toolkit:EventToCommandBehavior EventName="Appearing" Command="{Binding AppearingCommand}" BindingContext="{Binding Source={x:Reference MyPage}, Path=BindingContext}"/>
    </ContentPage.Behaviors>

But the OnAppearing() tasks is still never hit.

0 comments

1 answer

Your answer

Answer 1

Nancy Vo (WICLOUD CORPORATION) 8,155 Microsoft External Staff Moderator

Hello @Peter Stuart ,

Thanks for your question.

When updating to the .NET 10 Community Toolkit, Behaviors no longer connect to the ViewModel automatically. You correctly added BindingContext="{Binding Source={x:Reference MyPage}, Path=BindingContext}" to manually fix this.

However, the command may fail silently because it cannot find "MyPage".

I want to confirm again if you have added the name tag x:Name="MyPage" to your ContentPage at the very top of your XAML file.

<ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             x:Class="YourApp.Views.LoginPage"
             x:Name="MyPage"> ```

Please try this and let me know whether it resolves the issue. If not, I'd be happy to investigate further.

I hope this addresses your question. If this response was helpful, please consider following the guidance to provide feedback. Thank you.

Peter Stuart 0

Yes, I have added the Name tag

<?xml version="1.0" encoding="utf-8" ?>
<ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             xmlns:vm="clr-namespace:Badger.ViewModels"
             xmlns:dxe="clr-namespace:DevExpress.Maui.Editors;assembly=DevExpress.Maui.Editors"
             xmlns:toolkit="http://schemas.microsoft.com/dotnet/2022/maui/toolkit"
             xmlns:res="clr-namespace:Badger.Resources"
             Shell.NavBarIsVisible="False"
             x:Class="Badger.Views.DeviceLoginPage"
             x:Name="MyPage"
             x:DataType="vm:DeviceLoginViewModel">

    <ContentPage.Behaviors>
        <toolkit:EventToCommandBehavior Command="{Binding AppearingCommand}" EventName="Appearing" BindingContext="{Binding Source={x:Reference MyPage}, Path=BindingContext}" />
    </ContentPage.Behaviors>

Nancy Vo (WICLOUD CORPORATION) 8,155 Reputation points Microsoft External Staff Moderator

2026-07-10T07:35:45.6366667+00:00
Hi @Peter Stuart ,

Thanks for your update.

I recommend adding one small piece of code to the very end of your binding: x:DataType=ContentPage.

Because your page uses x:DataType="vm:DeviceLoginViewModel", the app assumes every binding belongs to your ViewModel. When the behavior searches for Path=BindingContext, it looks inside the ViewModel instead of the page, finds nothing, and stops silently.

<ContentPage.Behaviors> <toolkit:EventToCommandBehavior EventName="Appearing" Command="{Binding AppearingCommand}" BindingContext="{Binding Source={x:Reference MyPage}, Path=BindingContext, x:DataType=ContentPage}" /> </ContentPage.Behaviors>

Hope this helps.
Nancy Vo (WICLOUD CORPORATION) 8,155 Reputation points Microsoft External Staff Moderator

2026-07-14T02:54:55.9133333+00:00

Hi @Peter Stuart ,

I wonder if there is any update on this post. If you have any question, feel free to reach out. I'm happy to support you.
Nancy Vo (WICLOUD CORPORATION) 8,155 Reputation points Microsoft External Staff Moderator

2026-07-16T02:49:43.6533333+00:00

Hi @Peter Stuart ,

As I haven’t heard back from you for a while, I’ll go ahead and close this thread for now. If you still need assistance later, feel free to reach out.