Installation

Every package is a NuGet package containing a source generator and analyzers. There is nothing to configure beyond the package reference and one registration call.

Install

# The core. Everything else builds on it.
dotnet add package Immediate.Handlers

# Add whichever of these you need:
dotnet add package Immediate.Validations
dotnet add package Immediate.Apis
dotnet add package Immediate.Cache

# Pre-1.0: minor versions can include breaking changes.
dotnet add package Immediate.Jobs

# Independent of the above:
dotnet add package Immediate.Injections

The dependency graph

                    Immediate.Handlers
                  ▲       ▲       ▲       ▲
                  │       │       │       │
   Immediate.Validations  │  Immediate.Cache  Immediate.Jobs (0.x)
                          │
                    Immediate.Apis

   Immediate.Injections   (independent — see the note below)

• Immediate.Handlers is the core and depends on nothing but Microsoft.Extensions.DependencyInjection.Abstractions.
• Immediate.Validations, Immediate.Apis, Immediate.Cache and Immediate.Jobs each take a package reference on Immediate.Handlers, so it arrives transitively. Installing it explicitly as well is harmless and makes the intent clearer.
• Immediate.Apis additionally requires ASP.NET Core — use the Microsoft.NET.Sdk.Web SDK.
• Immediate.Cache requires IMemoryCache, registered with services.AddMemoryCache().
• Immediate.Jobs runs as a hosted service. It defaults to non-durable in-memory storage; add a provider package and configuration for production.
• Immediate.Injections requires none of the others.

Registration

Each package generates one assembly-level method, named after your assembly:

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddMyAppHandlers();   // Immediate.Handlers
builder.Services.AddMemoryCache();     // required by Immediate.Cache
builder.Services.AddMyAppCaches();     // Immediate.Cache
builder.Services.AddMyAppServices();   // Immediate.Injections
builder.Services.AddMyAppJobs();       // Immediate.Jobs (0.x)

var app = builder.Build();

app.MapMyAppEndpoints();               // Immediate.Apis

app.Run();

The MyApp part is derived from your assembly name and can be overridden — see The assembly identifier. Immediate.Validations has no registration method of its own; you add its ValidationBehavior<,> to your assembly-wide [Behaviors] list instead.

Supported target frameworks

The released packages multi-target net8.0, net9.0 and net10.0. Immediate.Jobs targets net8.0, net10.0 and net11.0.

Immediate.Jobs companion packages

Keep companion packages on the same version as Immediate.Jobs:

dotnet add package Immediate.Jobs.EntityFrameworkCore
dotnet add package Immediate.Jobs.LinqToDB
dotnet add package Immediate.Jobs.Redis
dotnet add package Immediate.Jobs.Dashboard
dotnet add package Immediate.Jobs.NodaTime
dotnet add package Immediate.Jobs.Testing

EF Core and LinqToDB provide full SQL-backed workflows; Redis provides distributed queues and recurring schedules without batch graphs or fair queues. Dashboard requires ASP.NET Core.

For the full matrix, including which packages require which companions, see Package compatibility.

Verifying the install

Build once, then inspect the generated code in your IDE. In Visual Studio, expand Dependencies → Analyzers; in Rider, expand Dependencies → Source Generators. See How source generation works for the generated file names.

Next

Head to the Quickstart for a working handler in five minutes, or start the tutorial to build a complete Todo API one package at a time.