Migrate everything to Azure.Messaging.ServiceBus

[Codare]

Hi,

When do we think that the Service Bus Explorer will be updated to use the Azure.Messaging.ServiceBus nuget package.

The Microsoft.Messaging.ServiceBus and WindowsAzure.ServiceBus client SDK's are now old and deprecated.

I would like to use an emulator link here: https://devopsifyme.com/simple-azure-service-bus-emulator-finally-here/
only when I provide the tool with a connection string I receive an error which states that I need to provide a fully qualified domain name "Endpoint".

I have tried using 127.0.0.1 and the port that the emulator runs on with no success. The port it requests is 443.

I am confident that once the latest sdk has been applied to the service bus explorer then things will begin to work properly.

I have been able to connect to the emulator from "Azure function apps" when the client libraries I used within them were the latest ones.

[SeanFeldman]

SBE is an old tool that started with the ASB SDK track 1, was migrated to track 2, and got stuck with adopting track 3 SDK (Azure.Messaging.ServiceBus). We've tried to adopt it in a few spots, but the issue is not updating the SDK. There's more.

1. The tool was built on Windows Forms. That's Windows-only technology that's not cross-platform (see Cross platform support #286)
2. The tool includes support for Service Bus, Event Hubs, Notification Hubs, and Relays. That's too much and needs to be broken out, IMO. But a decision was never reached on the topic.
3. This is a Free OSS project maintained by @paolosalvatori (original author) and two volunteers (@ErikMogensen and @SeanFeldman), with the help of various contributors submitting PRs.

As you can see from the list, the work is substantial here and requires a lot of commitment. If you need something to address your immediate problem, look at alternatives.

[TomasMalecek]

The migration to the new SDK seems to be tracked in #687.

Regarding the port... Haven't tested that, but are you sure you have unchecked the "Use AMQP Web Sockets fr Microsoft.Azure.ServiceBus.dll (new client)", @Codare? The "Web Sockets" part refers to port 443. See the docs.

The AMQP-over-WebSockets protocol option runs over port TCP 443 just like the HTTP/REST API, but is otherwise functionally identical with plain AMQP.