Shiny.Mediator.Caching.MicrosoftMemoryCache 4.4.0-beta-0021

Prefix Reserved
This is a prerelease version of Shiny.Mediator.Caching.MicrosoftMemoryCache.
There is a newer version of this package available.
See the version list below for details.
dotnet add package Shiny.Mediator.Caching.MicrosoftMemoryCache --version 4.4.0-beta-0021
                    
NuGet\Install-Package Shiny.Mediator.Caching.MicrosoftMemoryCache -Version 4.4.0-beta-0021
                    
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.Caching.MicrosoftMemoryCache" Version="4.4.0-beta-0021" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Shiny.Mediator.Caching.MicrosoftMemoryCache" Version="4.4.0-beta-0021" />
                    
Directory.Packages.props
<PackageReference Include="Shiny.Mediator.Caching.MicrosoftMemoryCache" />
                    
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.Caching.MicrosoftMemoryCache --version 4.4.0-beta-0021
                    
#r "nuget: Shiny.Mediator.Caching.MicrosoftMemoryCache, 4.4.0-beta-0021"
                    
#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.Caching.MicrosoftMemoryCache@4.4.0-beta-0021
                    
#: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.Caching.MicrosoftMemoryCache&version=4.4.0-beta-0021&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=Shiny.Mediator.Caching.MicrosoftMemoryCache&version=4.4.0-beta-0021&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 net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  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

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
4.10.0-beta-0020 192 9/19/2025
4.10.0-beta-0019 268 9/18/2025
4.10.0-beta-0018 258 9/18/2025
4.10.0-beta-0017 260 9/18/2025
4.10.0-beta-0016 265 9/18/2025
4.10.0-beta-0015 252 9/18/2025
4.10.0-beta-0014 261 9/18/2025
4.10.0-beta-0013 263 9/18/2025
4.10.0-beta-0012 272 9/18/2025
4.10.0-beta-0011 281 9/16/2025
4.10.0-beta-0010 279 9/16/2025
4.10.0-beta-0009 138 9/10/2025
4.10.0-beta-0008 132 9/10/2025
4.10.0-beta-0007 134 9/9/2025
4.10.0-beta-0006 184 8/28/2025
4.10.0-beta-0005 95 8/22/2025
4.10.0-beta-0004 125 8/22/2025
4.10.0-beta-0003 135 8/18/2025
4.10.0-beta-0002 142 8/18/2025
4.10.0-beta-0001 112 7/29/2025
4.9.1 266 7/29/2025
4.9.0 225 7/26/2025
4.9.0-beta-0005 540 7/22/2025
4.9.0-beta-0004 543 7/22/2025
4.9.0-beta-0003 538 7/22/2025
4.9.0-beta-0002 487 7/21/2025
4.9.0-beta-0001 419 7/21/2025
4.8.0 94 7/18/2025
4.8.0-beta-0004 94 7/18/2025
4.8.0-beta-0003 147 7/14/2025
4.8.0-beta-0002 147 7/14/2025
4.8.0-beta-0001 145 7/14/2025
4.7.0 234 6/25/2025
4.7.0-beta-0026 146 7/13/2025
4.7.0-beta-0025 146 7/10/2025
4.7.0-beta-0023 155 6/25/2025
4.7.0-beta-0022 152 6/24/2025
4.7.0-beta-0021 154 6/23/2025
4.7.0-beta-0020 151 6/19/2025
4.7.0-beta-0004 151 6/19/2025
4.6.6 159 6/19/2025
4.6.5 153 6/19/2025
4.6.4 155 6/19/2025
4.6.3 153 6/18/2025
4.6.2 152 6/18/2025
4.6.1 155 6/16/2025
4.6.1-beta-0005 153 6/18/2025
4.6.1-beta-0003 145 6/18/2025
4.6.1-beta-0001 149 6/16/2025
4.6.0 155 6/16/2025
4.5.0 303 6/10/2025
4.5.0-beta-0007 298 6/10/2025
4.5.0-beta-0006 277 6/9/2025
4.5.0-beta-0004 113 6/6/2025
4.5.0-beta-0002 143 6/6/2025
4.4.0 157 6/3/2025
4.4.0-beta-0025 153 6/3/2025
4.4.0-beta-0023 159 5/29/2025
4.4.0-beta-0021 160 5/29/2025
4.4.0-beta-0018 158 5/26/2025
4.4.0-beta-0017 154 5/26/2025
4.4.0-beta-0015 159 5/26/2025
4.4.0-beta-0014 159 5/26/2025
4.4.0-beta-0004 106 5/25/2025
4.2.2 196 5/24/2025
4.2.1 211 5/8/2025
4.2.0 220 4/25/2025
4.2.0-beta-0010 162 5/8/2025
4.2.0-beta-0009 152 5/8/2025
4.2.0-beta-0008 112 4/25/2025
4.2.0-beta-0001 199 4/16/2025
4.1.0 169 3/28/2025
4.1.0-beta-0001 143 3/28/2025
4.0.4 424 3/24/2025
4.0.4-beta-0001 418 3/24/2025
4.0.3 286 3/23/2025
4.0.3-beta-0007 279 3/23/2025
4.0.2 90 3/15/2025
4.0.1 230 3/5/2025
4.0.1-beta-0010 164 3/19/2025
4.0.1-beta-0009 89 3/15/2025
4.0.1-beta-0001 208 3/5/2025
4.0.0 228 3/4/2025
4.0.0-beta-0021 214 3/4/2025
4.0.0-beta-0017 215 3/4/2025
4.0.0-beta-0016 222 3/4/2025
4.0.0-beta-0010 103 3/2/2025
4.0.0-beta-0009 104 3/2/2025
4.0.0-beta-0002 112 3/1/2025
3.3.1 134 2/20/2025
3.3.0 116 2/20/2025
3.3.0-beta-0028 111 2/20/2025
3.3.0-beta-0025 112 2/19/2025
3.3.0-beta-0024 114 2/19/2025
3.3.0-beta-0004 109 2/8/2025
3.2.0 115 1/29/2025
3.2.0-beta-0027 108 1/29/2025
3.2.0-beta-0023 107 1/29/2025
3.2.0-beta-0020 105 1/29/2025
3.1.3 115 1/29/2025
3.1.2 123 1/28/2025
3.1.1 106 1/25/2025
3.1.0 118 1/25/2025
3.1.0-beta-0013 101 1/25/2025
3.1.0-beta-0006 106 1/25/2025
3.1.0-beta-0004 108 1/25/2025
3.0.0 111 1/24/2025
3.0.0-beta-0055 100 1/24/2025
3.0.0-beta-0046 109 1/23/2025
3.0.0-beta-0045 112 1/23/2025
3.0.0-beta-0043 109 1/23/2025
3.0.0-beta-0038 109 1/21/2025
3.0.0-beta-0037 89 1/21/2025
3.0.0-beta-0029 114 1/21/2025
3.0.0-beta-0028 106 1/21/2025
3.0.0-beta-0018 108 1/19/2025
3.0.0-beta-0016 87 1/14/2025
3.0.0-beta-0012 104 1/12/2025
3.0.0-beta-0008 117 1/2/2025
3.0.0-beta-0007 109 12/28/2024
3.0.0-beta-0004 111 12/22/2024