-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to Azure.Messaging.ServiceBus #201
Comments
Blocked by the Azure SDK team's decision to introduce plugins post GA. The API is internalized and won't be available. |
Just for your information: at work, we have updated to Azure Functions V4. I have upgraded most of this package to work with the new SDK: https://github.com/basilfx/ServiceBus.AttachmentPlugin/tree/feature/azure_messaging_servicebus Yes, this branch does not include the plugin capability, but we were not using it anyway (because of Azure Functions). |
@basilfx I'm no longer actively maintaining this project given the large message support provided officially by Microsoft. |
Here's a sample that demonstrates what an end-user experience would look like. cc @valdisiljuconoks |
Hi @SeanFeldman, we would love to have this feature available as an Azure Service Bus plugin. We use NSB over an ASB. Here's why we are looking for this feature for my team:
I hope the plugin would allow us to set the retention policy of external storage (I'm assuming it will be blob) and the naming convention of the blob name. This issue ](Particular/NServiceBus#6675) is stopping us from the NSB DataBus feature. So if the issue is fixed, perhaps we would not need this plugin anymore? (Not sure if the plugin would provide any additional features) |
Update 2023-02-11
Azure.Messaging.ServiceBus
SDK's approach to plugins has been refreshed. Details in the comment.Update 2020-06-26: blocked by the Azure SDK team's decision to introduce plugins post GA.
Azure Service Bus track 2 SDK is in preview and doesn't support pipelines and plugins yet.
Requires Preview 4 / Azure/azure-sdk-for-net#11986 to be completed first.
The text was updated successfully, but these errors were encountered: