Skip to main content

AOT / Trimming Support

NetMediate is fully compatible with NativeAOT-compiled and trimmed applications.

Summary​

Handler registration is generated at compile time by NetMediate.SourceGeneration — there is no assembly scanning and no reflection involved in registering handlers. Pipeline behaviors must be registered via RegisterBehavior<> on the builder; open-generic DI patterns are not supported.

PathAOT / Trim compatibleNotes
Source generation (AddNetMediate())✅ YesGenerated at compile time — no reflection
RegisterBehavior<TBehavior, TMessage, TResult>()✅ YesClosed-type — no reflection, fully AOT-safe

AOT-compatible setup​

Step 1: Install NetMediate with PrivateAssets="all"​

The source generator is bundled inside the NetMediate package. Activate it by setting PrivateAssets="all":

<PackageReference Include="NetMediate" Version="x.x.x" PrivateAssets="all" />
Required: PrivateAssets="all"

PrivateAssets="all" is required. Without it, the bundled source generator is not activated and AddNetMediate() will not be generated.

Step 2: Call the generated extension method​

// Generated at compile time — no reflection at startup
builder.Services.AddNetMediate();

The source generator discovers all handler types in your project and emits closed-type Register*Handler<> calls — fully AOT-safe.

Registering behaviors​

Register pipeline behaviors via the builder using closed types:

builder.Services.UseNetMediate(configure =>
{
    configure.RegisterBehavior<AuditBehavior<MyRequest, Task<MyResponse>>, MyRequest, Task<MyResponse>>();
});

AOT-unsafe patterns to avoid​

  • Calling MakeGenericType at runtime — not supported by NativeAOT
  • Using Type.GetGenericArguments() to construct service types at runtime
  • Registering behaviors via open-generic services.AddSingleton(typeof(IPipeline...<,>), typeof(...<,>)) — not supported