maui-dependency-injection

To configure dependency injection in .NET MAUI, you centralize service registrations in MauiProgram.cs. You define services, ViewModels, and Pages using appropriate lifetimes to ensure decoupled, testable code throughout your application.

Shell navigation resolves ViewModels and Pages with DI by automatically injecting registered dependencies when routing to a page. This requires properly registering your Pages and ViewModels in MauiProgram.cs before navigating.

Use AddSingleton, AddTransient, or AddScoped in MAUI based on desired service lifetimes. AddSingleton shares one instance app-wide, AddTransient creates a new instance each time, and AddScoped manages instances within a specific scope or request context.

Yes, you can register platform-specific service implementations in a .NET MAUI app. You use preprocessor directives in MauiProgram.cs to select and register the correct implementation per platform during compilation.

Dependency injection fails with XAML resources during MAUI App startup because of DI timing issues. XAML resources initialize before the DI container is fully built, requiring careful timing or late-bound resolution in App.CreateWindow to avoid resolution errors.

Interface-first design improves testability for .NET MAUI ViewModels by defining abstractions that enable mocking in unit tests. You can swap implementations without changing production code, ensuring constructor injection remains decoupled and test-friendly.