Sean Feldman
Sean Feldman
Do you have the C# code that generated the message? I'd like to see what was it. Don't need the whole repro, just the snippet that has created the message...
I'd want to see support for `CancellationToken` (#258) first 🙂.
Great suggestion. Also would cut down amount of work that has to be done today on the client-side to get a workaround.
@binzywu it introduced overhead that needs to be taken into consideration and coded each time. Because it's no longer a single message based operation, you need to have a transaction....
@jtaubensee I think you wanted to link to issue #6? 😉
Would this be considered for `1.0.0` or later?
Thanks @nemakam. Skipped that comment. So it could be then added to the [`2.0.0` milestone](https://github.com/Azure/azure-service-bus-dotnet/milestone/9) or `2.x` in case it has to be done after #6 is finished.
I'll need this feature as it will be blocking for scenarios where a message needs to be delayed and the **original** message ID has to be kept, but native-dedup is...
Server side work is tracked [here](https://github.com/Azure/azure-service-bus/issues/156).
@DarinMacRae `WindowsAzure.ServiceBus` is the old library (https://github.com/Azure/azure-service-bus) `Microsoft.Azure.ServiceBus` is the new library (this repo/issue tracker)