Skip to content

Getting started on managing Service Bus Publish-Subscribe with advanced features in C# - sessions, dead-lettering, de-duplication and auto-deletion of idle entries

License

Notifications You must be signed in to change notification settings

Azure-Samples/service-bus-dotnet-manage-publish-subscribe-with-advanced-features

Repository files navigation

page_type languages products extensions
sample
csharp
azure
services platforms
Service-Bus
dotnet

Getting started on managing Service Bus Publish-Subscribe with advanced features in C# - sessions, dead-lettering, de-duplication and auto-deletion of idle entries

Azure Service Bus basic scenario sample.

  • Create namespace.
  • Create a service bus subscription in the topic with session and dead-letter enabled.
  • Create another subscription in the topic with auto deletion of idle entities.
  • Create second topic with new Send Authorization rule, partitioning enabled and a new Service bus Subscription.
  • Update second topic to change time for AutoDeleteOnIdle time, without Send rule and with a new manage authorization rule.
  • Get the keys from default authorization rule to connect to topic.
  • Delete a topic
  • Delete namespace

For more on how to use Azure Service Bus see the samples for sending and receiving messages.

Running this Sample

To run this sample:

Set the environment variable AZURE_AUTH_LOCATION with the full path for an auth file. See how to create an auth file.

git clone https://github.com/Azure-Samples/service-bus-dotnet-manage-publish-subscribe-with-advanced-features.git

cd service-bus-dotnet-manage-publish-subscribe-with-advanced-features

dotnet build

bin\Debug\net452\ServiceBusPublishSubscribeAdvanceFeatures.exe

More information

Azure Management Libraries for C# Azure .Net Developer Center If you don't have a Microsoft Azure subscription you can get a FREE trial account here


This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.