maui-dependency-injection

To register Pages and ViewModels for dependency injection in .NET MAUI, configure your services in MauiProgram.cs and register pages for Shell navigation to enable automatic DI resolution. Use Transient lifetimes for Page/ViewModel pairs to ensure fresh instances during navigation.

You should avoid AddScoped for managing service lifetimes in MAUI because the framework lacks per-page scopes, making scoped lifetimes unreliable. Use AddSingleton for shared services and AddTransient for Page/ViewModel pairs to ensure application stability.

Shell navigation resolves dependencies automatically in MAUI by leveraging registered Page and ViewModel pairs during the routing process. When a page is navigated to, the DI container injects the required services via constructor injection based on your registration patterns.

Null reference exceptions during MAUI navigation are typically caused by unregistered pages. If a page is not properly registered in the dependency injection container before attempting Shell navigation, the framework cannot resolve the required dependencies and returns nulls at runtime.

To handle platform-specific service registrations safely in .NET MAUI, apply proper lifetime decisions and ensure safe timing of service resolution. Register platform-specific services coherently within your DI container to avoid runtime nulls and maintain testability.

Explicit service resolution in MAUI is needed when constructor injection is insufficient or the timing of service resolution requires direct access. Use explicit resolution carefully to satisfy specific dependencies while avoiding anti-patterns related to unregistered pages and scoped lifetimes.