Shiny.Mediator.AppSupport 4.2.0-beta-0010

Prefix Reserved
This is a prerelease version of Shiny.Mediator.AppSupport.
There is a newer version of this package available.
See the version list below for details.
dotnet add package Shiny.Mediator.AppSupport --version 4.2.0-beta-0010
                    
NuGet\Install-Package Shiny.Mediator.AppSupport -Version 4.2.0-beta-0010
                    
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="Shiny.Mediator.AppSupport" Version="4.2.0-beta-0010" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Shiny.Mediator.AppSupport" Version="4.2.0-beta-0010" />
                    
Directory.Packages.props
<PackageReference Include="Shiny.Mediator.AppSupport" />
                    
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 Shiny.Mediator.AppSupport --version 4.2.0-beta-0010
                    
#r "nuget: Shiny.Mediator.AppSupport, 4.2.0-beta-0010"
                    
#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 Shiny.Mediator.AppSupport@4.2.0-beta-0010
                    
#: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=Shiny.Mediator.AppSupport&version=4.2.0-beta-0010&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=Shiny.Mediator.AppSupport&version=4.2.0-beta-0010&prerelease
                    
Install as a Cake Tool

Shiny Mediator

<a href="https://www.nuget.org/packages/Shiny.Mediator" target="_blank"> <img src="https://img.shields.io/nuget/v/Shiny.Mediator?style=for-the-badge" /> </a>

Mediator is a behavioral design pattern that lets you reduce chaotic dependencies between objects. The pattern restricts direct communications between the objects and forces them to collaborate only via a mediator object.

Shiny Mediator <NugetBadge name="Shiny.Mediator" /> is a mediator pattern implementation, but for built with ALL .NET apps in mind. We provide a TON of middleware out-of-box to get you up and rolling with hardly any effort whatsoever. Checkout our Getting Started guide to see how easy it is. Imagine using 1 line of code to add offline, caching, or validation to your code!

This project is heavily inspired by MediatR with some lesser features that we feel were aimed more at server scenarios, while also adding some features we feel benefit apps

Samples & Documentation

Features

Works With

  • .NET MAUI - all platforms
  • MVVM Frameworks like Prism, ReactiveUI, & .NET MAUI Shell
  • Blazor - Work In Progress
  • Any other .NET platform - but you'll have to come up with your own "event collector" for the out-of-state stuff

What Does It Solve

Problem #1 - Service & Reference Hell

Does this look familiar to you? Look at all of those injections! As your app grows, the list will only grow. I feel sorry for the dude that gets to unit test this bad boy.

public class MyViewModel(
    IConnectivity conn,
    IDataService data,
    IAuthService auth,
    IDialogsService dialogs,
    ILogger<MyViewModel> logger
) {
    // ...
    try {
        if (conn.IsConnected) 
        {
            var myData = await data.GetDataRequest();
        }
        else 
        {
            dialogs.Show("No Connection");
            // cache?
        }
    }
    catch (Exception ex) {
        dialogs.Show(ex.Message);
        logger.LogError(ex);
    }
}

With a bit of our middleware and some events, you can get here:

public class MyViewModel(IMediator mediator) : IEventHandler<ConnectivityChangedEvent>, IEventHandler<AuthChangedEvent> {
    // ...
    var myData = await mediator.Request(new GetDataRequest());

    // logging, exception handling, offline caching can all be bundle into one nice clean call without the need for coupling
}

public class GetDataRequestHandler : IRequestHandler<GetDataRequest, MyData> {

    [OfflineAvailable] // <= boom done
    public async Task<MyData> Handle(GetDataRequest request, CancellationToken cancellationToken) {
        // ...
    }
}

Problem #2 - Messages EVERYWHERE (+ Leaks)

Do you use the MessagingCenter in Xamarin.Forms? It's a great tool, but it can lead to some memory leaks if you're not careful. It also doesn't have a pipeline, so any errors in any of the responders will crash the entire chain. It doesn't have a request/response style setup (not that it was meant for it), but this means you still require other services.

public class MyViewModel
{
    public MyViewModel()
    {
        MessagingCenter.Subscribe<SomeEvent1>(this, @event => {
            // do something
        });
        MessagingCenter.Subscribe<SomeEvent2>(this, @event => {
            // do something
        });

        MessagingCenter.Send(new SomeEvent1());
        MessagingCenter.Send(new SomeEvent2());

        // and don't forget to unsubscribe
        MessagingCenter.Unsubscribe<SomeEvent1>(this);
        MessagingCenter.Unsubscribe<SomeEvent2>(this);
    }
}

Let's take a look at our mediator in action for this scenarios

public class MyViewModel : IEventHandler<SomeEvent1>, IEventHandler<SomeEvent2>
{
    public MyViewModel(IMediator mediator)
    {
        // no need to unsubscribe
        mediator.Publish(new SomeEvent1());
        mediator.Publish(new SomeEvent2());
    }
}

Problem #3 - Strongly Typed Navigation with Strongly Typed Arguments

Our amazing friends over in Prism offer the "best in class" MVVM framework. We'll them upsell you beyond that, but one of their amazing features is 'Modules'. Modules help break up your navigation registration, services, etc.

What they don't solve is providing a strongly typed nature for this stuff (not their job though). We think we can help addon to their beautiful solution.

A normal call to a navigation service might look like this:

_navigationService.NavigateAsync("MyPage", new NavigationParameters { { "MyArg", "MyValue" } });

This is great. It works, but I don't know the type OR argument requirements of "MyPage" without going to look it up. In a small project with a small dev team, this is fine. In a large project with a large dev team, this can be difficult.

Through our Shiny.Framework library we offer a GlobalNavigationService that can be used to navigate to any page in your app from anywhere, however, for the nature of this example, we'll pass our navigation service FROM our viewmodel through the mediator request to ensure proper scope.

public record MyPageNavigatonRequest(INavigationService navigator, string MyArg) : IRequest;
public class MyPageNavigationHandler : IRequestHandler<MyPageNavigatonRequest>
{
    public async Task Handle(MyPageNavigatonRequest request, CancellationToken cancellationToken)
    {
        await request.navigator.NavigateAsync("MyPage", new NavigationParameters { { "MyArg", request.MyArg } });
    }
}

Now, in your viewmodel, you can do this:

public class MyViewModel
{
    public MyViewModel(IMediator mediator)
    {
        mediator.Request(new MyPageNavigationCommand(_navigationService, "MyValue"));
    }
}

Strongly typed. No page required page knowledge from the module upfront. The other dev team of the module can define HOW things work.

Product Compatible and additional computed target framework versions.
.NET net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  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 (3)

Showing the top 3 NuGet packages that depend on Shiny.Mediator.AppSupport:

Package Downloads
Shiny.Mediator.Maui

Shiny Mediator - A mediator pattern for all .NET Apps

Shiny.Mediator.Blazor

Shiny Mediator - A mediator pattern for all .NET Apps

Shiny.Mediator.Uno

Shiny Mediator - A mediator pattern for all .NET Apps

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.10.0-beta-0006 179 8/28/2025
4.10.0-beta-0005 95 8/22/2025
4.10.0-beta-0004 128 8/22/2025
4.10.0-beta-0003 134 8/18/2025
4.10.0-beta-0002 130 8/18/2025
4.10.0-beta-0001 98 7/29/2025
4.9.1 227 7/29/2025
4.9.0 216 7/26/2025
4.9.0-beta-0005 494 7/22/2025
4.9.0-beta-0004 493 7/22/2025
4.9.0-beta-0003 491 7/22/2025
4.9.0-beta-0002 461 7/21/2025
4.9.0-beta-0001 385 7/21/2025
4.8.0 84 7/18/2025
4.8.0-beta-0004 71 7/18/2025
4.8.0-beta-0003 168 7/14/2025
4.8.0-beta-0002 151 7/14/2025
4.8.0-beta-0001 144 7/14/2025
4.7.0 287 6/25/2025
4.7.0-beta-0026 148 7/13/2025
4.7.0-beta-0025 149 7/10/2025
4.7.0-beta-0024 140 6/25/2025
4.7.0-beta-0023 153 6/25/2025
4.7.0-beta-0022 148 6/24/2025
4.7.0-beta-0021 157 6/23/2025
4.7.0-beta-0020 151 6/19/2025
4.7.0-beta-0004 151 6/19/2025
4.6.6 168 6/19/2025
4.6.5 154 6/19/2025
4.6.4 154 6/19/2025
4.6.3 160 6/18/2025
4.6.2 164 6/18/2025
4.6.1 176 6/16/2025
4.6.1-beta-0005 157 6/18/2025
4.6.1-beta-0003 155 6/18/2025
4.6.1-beta-0001 151 6/16/2025
4.6.0 156 6/16/2025
4.5.0 308 6/10/2025
4.5.0-beta-0007 294 6/10/2025
4.5.0-beta-0006 280 6/9/2025
4.5.0-beta-0004 115 6/6/2025
4.5.0-beta-0002 145 6/6/2025
4.4.0 280 6/3/2025
4.4.0-beta-0025 162 6/3/2025
4.4.0-beta-0023 158 5/29/2025
4.4.0-beta-0021 158 5/29/2025
4.4.0-beta-0018 167 5/26/2025
4.4.0-beta-0017 156 5/26/2025
4.4.0-beta-0015 158 5/26/2025
4.4.0-beta-0014 166 5/26/2025
4.4.0-beta-0004 116 5/25/2025
4.2.2 237 5/24/2025
4.2.1 257 5/8/2025
4.2.0 251 4/25/2025
4.2.0-beta-0010 164 5/8/2025
4.2.0-beta-0009 154 5/8/2025
4.2.0-beta-0008 118 4/25/2025
4.2.0-beta-0001 216 4/16/2025
4.1.0 239 3/28/2025
4.1.0-beta-0001 148 3/28/2025
4.0.4 438 3/24/2025
4.0.4-beta-0001 413 3/24/2025
4.0.3 292 3/23/2025
4.0.3-beta-0007 283 3/23/2025
4.0.2 170 3/15/2025
4.0.1 262 3/5/2025
4.0.1-beta-0010 170 3/19/2025
4.0.1-beta-0009 88 3/15/2025
4.0.1-beta-0001 230 3/5/2025
4.0.0 245 3/4/2025
4.0.0-beta-0021 231 3/4/2025
4.0.0-beta-0017 217 3/4/2025
4.0.0-beta-0016 228 3/4/2025
4.0.0-beta-0010 112 3/2/2025
4.0.0-beta-0009 118 3/2/2025
4.0.0-beta-0002 114 3/1/2025
3.3.1 238 2/20/2025
3.3.0 128 2/20/2025
3.3.0-beta-0028 108 2/20/2025
3.3.0-beta-0025 125 2/19/2025
3.3.0-beta-0024 121 2/19/2025
3.3.0-beta-0004 108 2/8/2025
3.2.0 219 1/29/2025
3.2.0-beta-0027 101 1/29/2025
3.2.0-beta-0023 95 1/29/2025
3.2.0-beta-0020 97 1/29/2025
3.1.3 135 1/29/2025
3.1.2 116 1/28/2025
3.1.1 115 1/25/2025
3.1.0 129 1/25/2025
3.1.0-beta-0013 103 1/25/2025
3.1.0-beta-0006 107 1/25/2025
3.1.0-beta-0004 110 1/25/2025
3.0.0 115 1/24/2025
3.0.0-beta-0055 108 1/24/2025
3.0.0-beta-0046 109 1/23/2025
3.0.0-beta-0045 106 1/23/2025
3.0.0-beta-0043 110 1/23/2025
3.0.0-beta-0038 112 1/21/2025
3.0.0-beta-0037 104 1/21/2025
3.0.0-beta-0029 102 1/21/2025
3.0.0-beta-0028 114 1/21/2025
3.0.0-beta-0018 106 1/19/2025
3.0.0-beta-0016 81 1/14/2025
3.0.0-beta-0012 99 1/12/2025
3.0.0-beta-0008 108 1/2/2025
3.0.0-beta-0007 115 12/28/2024
3.0.0-beta-0004 111 12/22/2024
2.2.0-beta-0001 313 10/28/2024
2.1.1 546 10/28/2024
2.1.0 269 10/19/2024
2.1.0-beta-0016 115 10/19/2024
2.1.0-beta-0015 116 10/19/2024
2.1.0-beta-0014 137 10/19/2024
2.1.0-beta-0013 123 10/19/2024
2.1.0-beta-0011 139 10/18/2024
2.1.0-beta-0010 138 10/18/2024
2.1.0-beta-0004 112 10/8/2024
2.1.0-beta-0002 109 10/6/2024
2.0.2 159 10/6/2024
2.0.1 126 10/6/2024
2.0.0 200 10/4/2024
2.0.0-beta-0060 114 10/6/2024
2.0.0-beta-0059 108 10/6/2024
2.0.0-beta-0056 106 10/4/2024
2.0.0-beta-0054 123 10/3/2024
2.0.0-beta-0053 106 10/2/2024
2.0.0-beta-0052 121 10/2/2024
2.0.0-beta-0050 111 10/2/2024
2.0.0-beta-0049 119 10/2/2024
2.0.0-beta-0046 119 10/1/2024
2.0.0-beta-0044 127 9/30/2024
2.0.0-beta-0026 129 9/24/2024
2.0.0-beta-0023 116 9/23/2024
2.0.0-beta-0022 104 9/23/2024
2.0.0-beta-0020 133 9/22/2024
2.0.0-beta-0004 118 9/20/2024
2.0.0-beta-0003 119 9/20/2024