The following samples contain variants for both .NET Core and .NET Framework.
Both solutions are contained within the same zip file, and use the same underlying C# files, but with separate . and . files.
For example, the Full Duplex sample download will contain:
- FullDuplex.sln - Solution for .NET Framework
- FullDuplex.Core.sln - Solution for .NET Core
- Server - Project directory
- Server.csproj - Project for .NET Framework
- Server.Core.csproj - Project for .NET Core
Be sure to review the general information about running samples.
Recommended samples
To get started with .NET Core and NServiceBus, the following samples are recommended:
General samples
- Full Duplex - sending and receiving with NServiceBus endpoints
- Publish/Subscribe - publishing events to multiple subscribers
- Simple Saga Usage
- Using NServiceBus in a .NET Core 3.1 Generic host
- Using NServiceBus in an ASP.NET Core WebAPI Application
- Hosting endpoints in Docker Linux containers
- ASP.NET Core 3 Dependency Injection Integration
Message transport samples
- Simple RabbitMQ Transport Usage
- Simple SQL Server Transport Usage
- Azure Storage Queues Transport
- Simple AmazonSQS Transport Usage
Persistence samples
All .NET Core Samples
This is the comprehensive list of samples that support .NET Core:
- Appending username using headers
- Automatic Retries
- Building a Custom Feature
- Building endpoints with .NET Core 3.1
- Callback Usage
- Consumer-driven Contracts
- Custom Exception Handling
- Customization with MEF or Reflection
- Delayed Delivery
- Distributed tracing with Azure Monitor Application Insights
- Endpoint configuration choices
- Entity Framework Core integration with SQL Persistence
- Fault Tolerance
- File Share Data Bus Usage
- Full Duplex
- Gateway
- Header Manipulation
- Immutable Messages samples
- Message Mutators
- Message Throughput Throttling
- Performance Counter Usage
- Routing Slips
- SQL Server Transport and SQL Persistence
- Startup and Shutdown Sequence
- Unit of Work Usage
- Unit Testing a custom recoverability policy
- Unit Testing NServiceBus
- Unobtrusive
- Add feature toggles to handlers
- Add handler timing pipeline
- ASP.NET Core 3 Dependency Injection Integration
- Audit Filter Pipeline Extension
- Autofac Dependency Injection Usage
- Azure Blob Storage Data Bus Cleanup with Azure Functions
- Azure Blob Storage DataBus
- Azure Service Bus lock renewal
- Azure Service Bus Native Integration
- Azure Service Bus Pub/Sub Native Integration
- Azure Service Bus Send/Reply Sample
- Azure Storage Queues Transport
- Change/Move Message Type
- Command routing
- CommonLogging Usage
- Control of serialization via the pipeline
- Custom Log4Net appender
- Custom Logger Factory
- Custom mapping
- Custom NLog configuration
- Custom Serializer for Data Bus
- Default Logging
- Dispatch notification pipeline extension
- Endpoint hosting with the Generic Host
- Externally Managed Mode
- FluentScheduler Usage
- Forwarding address
- Generic Host multiple endpoint hosting
- Handling Stream Properties Via the Pipeline
- Hangfire Usage
- Hosting endpoints in Docker Linux containers
- Injecting tenant-aware components into message handlers
- Long-running operations with Azure Service Bus Transport
- Message body encryption
- Message forwarding
- Message property encryption
- Message signing using the pipeline
- MongoDB Persistence
- Monitor Azure Storage Queues endpoints with ServiceControl adapter
- Monitor ServiceControl events with Azure Application Insights
- Monitor third-party systems with custom checks
- Monitor with ServiceControl events
- Multiple Deserializers
- Native integration
- Native integration with AmazonSQS Transport
- Native Integration with Azure Storage Queues Transport
- Native integration with RabbitMQ
- Native Publish/Subscribe
- Newtonsoft Bson Serializer
- Newtonsoft JSON Serializer
- NHibernate persistence in multi-tenant systems
- Ninject Dependency Injection Usage
- Notifications
- NServiceBus.Extensions.DependencyInjection Usage
- NServiceBus.Extensions.Logging Usage
- On-Premises Showcase
- Propagating Tenant Information to Downstream Endpoints
- Quartz.NET Usage
- Repair malformed messages using pipeline behavior
- Repair malformed messages using ServiceControl retry redirects
- Report metrics to Azure Monitor Application Insights
- Scheduler
- Scheduling with Timers
- Self-Hosting in Azure WebJobs
- Session filter pipeline extension
- Simple AmazonSQS Transport usage
- Simple NHibernate Persistence Usage
- Simple RabbitMQ Transport Usage
- Simple RavenDB Persistence Usage
- Simple Saga Usage
- Simple SQL Persistence Usage
- Simple SQL Server transport usage
- SQL Persistence in multi-tenant system
- SQL Persistence Saga Finding Logic
- SQL Persistence Saga Rename
- SQL Server Transport Startup Purge Behavior
- Stack Trace Cleaning
- StructureMap Dependency Injection Usage
- Transition serialization formats
- Transitioning Saga Correlation IDs
- Unit of work using the pipeline
- Unity Dependency Injection Usage
- Unobtrusive property encryption
- Using NServiceBus in an ASP.NET Core Web Application
- Using NServiceBus in an ASP.NET Core WebAPI Application
- Using NServiceBus in Azure Functions with Service Bus triggers
- Using NServiceBus with ASP.NET MVC
- Using Outbox with RabbitMQ
- Using Outbox with SQL Server
- Windsor Dependency Injection Usage
- XML Serializer
- Azure Table Persistence Usage using Saga IDs as partition key
- Azure Table Persistence Usage with transactions
- AzureTable Persistence Usage with non-default table
- Cosmos DB Persistence Usage with non-default container
- Cosmos DB Persistence Usage with transactions
- Simple Azure Table Persistence Usage
- Simple Cosmos DB Persistence Usage
- Using NServiceBus in AWS Lambda with SQS