configuring-avalonia-dependency-injection

Add dependency injection to AvaloniaUI by creating a GenericHost with Host.CreateDefaultBuilder in App.axaml.cs, registering services and ViewModels in ConfigureServices, then resolving the MainWindow from the host's service provider during OnFrameworkInitializationCompleted.

Register the ViewModel with services.AddTransient and the Window with services.AddSingleton, then add the ViewModel as a constructor parameter in the Window. Set DataContext to the injected ViewModel inside the constructor after InitializeComponent.

Yes, AvaloniaUI works with Microsoft.Extensions.Hosting by building the host inside OnFrameworkInitializationCompleted. The same GenericHost pattern used in WPF applies, giving access to configuration, logging, and the DI container.

ViewModels are typically registered as transient so each Window resolution gets a fresh instance, while shared services like repositories use singleton. The template registers MainViewModel with AddTransient and MainWindow with AddSingleton.

Yes, ViewModels can live in a UI-framework-independent class library referencing only CommunityToolkit.Mvvm. The Avalonia app project references this library and registers the ViewModels in its DI container, keeping presentation logic testable and portable.