maui-dependency-injection

To configure dependency injection in .NET MAUI, register services with their lifetimes in MauiProgram.cs and inject them via constructors in pages and view models. This enables automatic resolution and testability across your application.

Yes, Shell navigation resolves dependencies automatically in MAUI for registered routes. Pages and view models are instantiated with their constructor dependencies injected by the DI container during Shell-based navigation.

Register platform-specific services in MAUI using preprocessor directives in MauiProgram.cs. This targets individual platform implementations while maintaining interface-first testability patterns for your shared code.

XAML resource parsing fails with dynamic dependency resolution due to timing issues during initialization. This known gotcha occurs because XAML resources instantiate before the MAUI dependency container is fully built and ready.

Choose service lifetimes in MAUI dependency injection by evaluating scope needs: Singleton shares one instance app-wide, Transient creates a new instance each time, and Scoped matches a specific context to improve testability and maintainability.

Yes, the interface-first pattern works for testing MAUI view models by registering interfaces rather than concrete classes. This enables easy mocking and substitution of dependencies during unit tests.