azureservicebus

I have created a very simple console application that connects to Azure ServiceBus and sends one message. I tried the latest library from Microsoft ( Microsoft.Azure.ServiceBus ) but no matter what I do I just get this error: No connection could be made because the target machine actively refused it ErrorCode: ConnectionRefused I have tried exactly the same connection string in Service Bus Explorer and it does work just fine. Moreover I connected without problems using the older library from Microsoft ( WindowsAzure.ServiceBus ). var sender = new MessageSender("endpoint", "topicName"); sender

MS has recently introduced the Microsoft.Azure.ServiceBus namespace. https://github.com/Azure/azure-service-bus/blob/master/samples/readme.md It is geared for the new .net standard framework (as if MS doesn't have enough semi-redundant code bases) My question is, how much better could it be in terms of performance? I can say with confidence, that the Microsoft.ServiceBus.Messaging leaves lots to be desired, in particular when it comes to persistent receiving. A very useful feature of the Microsoft.ServiceBus.Messaging , is the message pump, built on top of OnMessage() method. The new library,

I've got started with Azure Service Bus in Azure. Having gone through some references over the Internet, it seems that people use BrokeredMessage class in Microsoft.ServiceBus.Messaging rather than Message class in Microsoft.Azure.ServiceBus. BrokeredMessage class: https://docs.microsoft.com/en-us/dotnet/api/microsoft.servicebus.messaging.brokeredmessage?view=azure-dotnet Message class: https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.servicebus.message?view=azure-dotnet I can send both of message 'types' to Azure Service Bus and also work with them over Azure Service Bus. Also,

I'm trying to read a message from an Azure ServiceBus queue using an Azure WebJob but it's throwing and exception: Unhandled Exception: System.InvalidOperationException: Found 2 DNS claims in authorization context. I've set the correct connection strings named "AzureWebJobsServiceBus", "AzureWebJobsDashboard" and "AzureWebJobsStorage" The WebJob Program code has been updated to use JobHostConfiguration: class Program { static void Main() { var config = new JobHostConfiguration(); config.UseServiceBus(); var host = new JobHost(config); host.RunAndBlock(); } } And the actual Job method public

Is there a way to play with and discover Azure Service Bus on the local emulator without registering to the real Azure Services? I was following a tutorial on the use of the Azure Service Bus but at a certain point a Namespace and an Issuer Name and Key is required. I don't have that data since I'm not registered to Azure Services and I don't want to do it now ( I will get my trial when I will feel ready to develop/test something real ). SliverNinja - MSFT Unfortunately there is not an emulated Azure Service Bus you can run locally. The Azure Service Bus requires an active Azure Subscription .

I've been learning about Event Hubs and just want to get confirmation or correction on my perspective on Event Hubs? I’m used to leveraging retries, poison messages, at least once delivery and so on for normal enterprise messaging solutions, which Azure Service Bus Queues and Topics give me. It seems that Event Hubs is intended to provide a different tool for very high scale where you have to give up a little of the more “enterprise” features for much higher scale. Am I thinking about this correctly? Are there additional specifics I need to consider as well? I realize there could be some