Migration Guides
Dispatch provides migration paths from popular .NET messaging libraries. Each guide covers the key differences, mapping tables, and step-by-step instructions to help you transition smoothly.
Before You Start
- .NET 10.0
- Install the required packages:
dotnet add package Excalibur.Dispatch
- Familiarity with Getting Started and Core Concepts
Available Migration Guides
- From MediatR -- Migrate request/response and notification patterns to Dispatch actions and events.
- From MassTransit -- Migrate consumers, sagas, and transport configuration to Dispatch equivalents.
- From NServiceBus -- Migrate handlers, sagas, and pipeline behaviors to the Dispatch model.
- From ASP.NET Eventing Proposal -- Migrate from the ASP.NET eventing proposal pattern.
Framework Migrations
- Migrating to .NET 10 -- Sprint 797 collapsed every shipping package to
net10.0. Consumer project TFM, SDK, Docker images, and serverless runtime identifiers must be updated.
Reference
- Version Upgrades -- Versioning policy and current registration API reference.
- MessageContext Guide -- Using IMessageContext direct properties for type-safe, high-performance message context access.
See Also
- Getting Started — New project setup from scratch
- Core Concepts — Excalibur framework fundamentals