Provide Static MauiContextAccessor

Description

The root application types used by Maui are prescriptive in accessing a Current instance to get the Application Scope IServiceProvider and a reference to IApplication. While this works for Maui Applications it causes problems in Embedding scenarios where the Android MauiApplication or the Windows MauiWinUIApplication for instance will not exist.

(Public) API Changes

static MauiContextAccessor

Properties

API	Description
Services	Gets or sets the IServiceProvider.
Application	Gets or sets the IApplication.

Usage Scenarios

This provides a single class that can be accessed from:

• Markup Extensions
• Embedding Scenarios
• Existing native Maui Application classes

Backward Compatibility

This can be added so that under the covers the existing native Maui Application classes such as the Android MauiApplication or the MauiWinUIApplication can use this when getting/setting the Services/Application properties.

public abstract class MauiWinUIApplication : UI.Xaml.Application, IPlatformApplication
{
    public IServiceProvider Services
    {
        get => MauiContextAccessor.Services;
        protected set => MauiContextAccessor.Services = value;
    }

    public IApplication Application
    {
        get => MauiContextAccessor.Application;
        protected set => MauiContextAccessor.Application = value;
    }
}

Difficulty

Low

[Eilon]

@dansiegel yeah thanks I did see that other PR. I’m not sure I’m a big fan of that either because of the problems it can create, but I guess it was already there…

[Eilon]

Hmm this is somewhat of an anti-pattern. The whole idea is to never have static instances of these available. But if you do want one, isn’t there some kind of Application.Current.<something> that you could use?