NServiceBus icon indicating copy to clipboard operation
NServiceBus copied to clipboard

Build, version, and monitor better microservices with the most powerful service platform for .NET

Results 217 NServiceBus issues
Sort by recently updated
recently updated
newest added

https://github.com/Particular/NServiceBus/blob/26388902447f0e567011615980dad124bd90a714/src/NServiceBus.Core/Recoverability/DelayedRetry.cs#L38

Improvement

Looking forward to the next major version of `NServiceBus`. I was surprised to see that you are dropping support for `netstandard2.0` - what is the rational for this? It looks...

Sometimes you just want to do a simple test. Unfortunately, no out-of-the-box messages exist. Customers need to add some test messages and handlers and then redeploy. It would be nice...

Although we have the [databus](https://docs.particular.net/nservicebus/messaging/databus/) that works for the entire message. It would be nice to have the ability to add an attachment to a message instead. It will also...

Occasionally we see a need to copy headers from an incoming message to an outgoing message. The framework does this for a few headers already. i.e. `NServiceBus.ConversationId` is copied, `NServiceBus.MessageId`...

Add an exception that can be thrown, which is by default treated as an unrecoverable exception. // cc @SimonCropp

Improvement

The fileshare databus currently always generates new ID's. If the same data is passed multiple times a new blob is created. By using deterministic id's based on for example the...

The databus currently just stores any kind of blob, small and huge. Databus properties are there to solve issues with tranport message size limitations. If working on MSMQ than there...

When a message with databus properties is received the behavior currently will always fetch the databus blobs even though they might not even be used by the receiver. Having dynamic...

CSharp 8 introduced [nullable reference types](https://docs.microsoft.com/en-us/dotnet/csharp/nullable-references). Developers of libraries and frameworks can enable nullability and annotate their types and methods with [nullable attributes](https://docs.microsoft.com/en-us/dotnet/csharp/nullable-attributes) to make sure consumers of their APIs...