ShellInject 10.0.1

dotnet add package ShellInject --version 10.0.1
                    
NuGet\Install-Package ShellInject -Version 10.0.1
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="ShellInject" Version="10.0.1" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="ShellInject" Version="10.0.1" />
                    
Directory.Packages.props
<PackageReference Include="ShellInject" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add ShellInject --version 10.0.1
                    
#r "nuget: ShellInject, 10.0.1"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package ShellInject@10.0.1
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=ShellInject&version=10.0.1
                    
Install as a Cake Addin
#tool nuget:?package=ShellInject&version=10.0.1
                    
Install as a Cake Tool

ShellInject

ShellInject is a .NET MAUI library that makes Shell navigation feel effortless. It provides a clean, typed navigation API, wires ViewModels from XAML, and automatically delivers navigation data and lifecycle events. With a single startup line and a single attached property in XAML, your pages are ready to navigate, receive parameters, and stay lifecycle-aware without manual route registration or boilerplate setup.

Why use it? ShellInject keeps your ViewModels focused on behavior, not plumbing. It reduces navigation friction, enables consistent data passing in both directions, and scales cleanly as your app grows in complexity.

Highlights

  • Static ShellNavigation API that uses Shell.Current by default (or an explicit Shell if you prefer).
  • Automatic route registration for pages, no manual route strings.
  • ViewModel binding via a single attached property in XAML.
  • Reliable lifecycle hooks: appear, disappear, first-time initialization, and data delivery.
  • Built-in helpers for modals, tabs, popups, and back-navigation data.

Requirements

  • .NET MAUI Shell-based app.
  • If you use popups, install and register CommunityToolkit.Maui in your app.

Quick Start

1) Enable ShellInject

var builder = MauiApp.CreateBuilder();
builder
    .UseMauiApp<App>()
    .UseShellInject();

return builder.Build();

2) Bind a ViewModel in XAML

xmlns:extensions="clr-namespace:ShellInject.Extensions;assembly=ShellInject"
xmlns:vm="clr-namespace:YourApp.ViewModels"

extensions:ShellInjectPageExtensions.ViewModelType="{x:Type vm:MainViewModel}"
x:DataType="vm:MainViewModel"

ShellInject will resolve the ViewModel from DI if registered, otherwise it will create one and inject dependencies via ActivatorUtilities.

3) Inherit from ShellInjectViewModel

public class MainViewModel : ShellInjectViewModel
{
    public override Task InitializedAsync()
    {
        // First-time setup
        return Task.CompletedTask;
    }

    public override Task DataReceivedAsync(object? parameter)
    {
        // Forward navigation data
        return Task.CompletedTask;
    }

    public override Task ReverseDataReceivedAsync(object? parameter)
    {
        // Back navigation data
        return Task.CompletedTask;
    }
}

4) Navigate with ShellNavigation

await ShellNavigation.PushAsync<DetailsPage>(parameter: new { id = 123 });

ViewModel Lifecycle and Data Flow

ShellInject wires lifecycle and data delivery automatically for ViewModels that implement IShellInjectShellViewModel (already implemented by ShellInjectViewModel).

  • OnAppearing() and OnDisAppearing() are invoked on page appear/disappear.
  • OnAppearedAsync() runs after navigation completes.
  • InitializedAsync() runs once per ViewModel instance (first time it appears).
  • DataReceivedAsync(object? parameter) runs on forward navigation with a parameter.
  • ReverseDataReceivedAsync(object? parameter) runs when data is returned on back navigation.

ShellNavigation is the recommended entry point. It uses Shell.Current by default and throws a clear exception if a Shell cannot be found. If you use multiple windows, pass an explicit Shell instance.

await ShellNavigation.PushAsync<DetailsPage>(shell: myShell, parameter: data);

Pushing

ShellNavigation.PushAsync<TPageType>(parameter, animate);
ShellNavigation.PushMultiStackAsync(pageTypes, parameter, animate, animateAllPages);

Modals

ShellNavigation.PushModalWithNavigationAsync(page, parameter, animate);
ShellNavigation.PushModalAsync<TPageType>(parameter, animate);

Popping

ShellNavigation.PopAsync(parameter, animate);
ShellNavigation.PopModalStackAsync(data, animate);
ShellNavigation.PopToAsync<TPageType>(parameter);
ShellNavigation.PopToRootAsync(parameter, animate);

Popups

ShellNavigation.ShowPopupAsync<TPopup>(data, onError);
ShellNavigation.DismissPopupAsync<TPopup>(data);

Replace Root (Flyout)

ShellNavigation.ReplaceAsync<TPageType>(parameter, animate);

Tabs

ShellNavigation.ChangeTabAsync(tabIndex, parameter, popToRootFirst);

Helper

ShellNavigation.SendDataToPageAsync<TPageType>(data);

Data Return Example

// Details page
await ShellNavigation.PopAsync(parameter: "Saved!");

// Main view model
public override Task ReverseDataReceivedAsync(object? parameter)
{
    var message = parameter as string;
    return Task.CompletedTask;
}

Dependency Injection Helpers

var requiredService = Injector.GetRequiredService<ISampleService>();
var optionalService = Injector.GetService<ISampleService>();

Note: GetService returns null if the service is not registered.

Deprecated API

The old Shell extension methods are still available for backwards compatibility but are marked [Obsolete]. Use ShellNavigation for new code.

Troubleshooting

  • InvalidOperationException about Shell not found means Shell.Current is unavailable. Ensure your app is using a Shell as the root page, or pass an explicit Shell instance to ShellNavigation.
  • PushMultiStackAsync requires at least one page type in the list.

Sample

See the Sample project in this repository for end-to-end usage patterns.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-android36.0 is compatible.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-ios26.0 is compatible.  net10.0-maccatalyst was computed.  net10.0-maccatalyst26.0 is compatible.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
10.0.1 108 2/15/2026
10.0.0 208 12/22/2025
9.0.2 274 9/30/2025
9.0.1 242 8/8/2025
3.1.7 838 6/21/2025
3.1.6 453 4/8/2025
3.1.5 192 4/3/2025
3.1.4 191 3/20/2025
3.1.3 118 3/15/2025
3.1.2 178 2/13/2025
3.1.1 169 2/5/2025
3.1.0 177 2/3/2025
3.0.11 170 1/31/2025
3.0.10 150 1/29/2025
3.0.9 138 1/27/2025
3.0.8 140 1/27/2025
3.0.7 150 1/27/2025
3.0.6 138 1/23/2025
3.0.5 138 1/17/2025
3.0.4 487 11/1/2024
Loading failed

• Added ShellNavigation static API and deprecated Shell extension methods
           • Improved startup lifecycle handling and view model wiring
           • Shipped transitive MAUI/toolkit dependencies with .NET 10 baselines
           • Updated sample usage and documentation