.NET Standard2 support and Azure.Messaging.Servicebus SDK #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds:
.NET Standard 2
Azure.Messaging.Servicebus
SDK (the latest, and recommended, Azure Service Bus .NET SDK available)SourceLink
supportLinearRetryPolicy
with a TimeSpan array (to define custom waits between retries)QueuePollInterval
(to be able to have an additional timeout in case of low read timeouts and multiple queues)GlobalConfigurationExtensions
to play nice with .NETCoreServiceCollection
configurationreadme.md
I havent touched the appveyr.yml configuration file (i dont use appveyor). For sure it needs an update in order to compile this PR.
Also, i have removed the
MinSyncReceiveTimeout
fromServiceBusQueueJobQueue.cs
because with the new SDK, waiting for just 1 Tick doesnt work: no messages are retreived, moreover, i think that all the queues should honor theLoopReceiveTimeout
optionCloses #19, closes #18, closes #7, also fix #15