5.0.14

What's Changed

The only change compared to 5.0.12 is a small change to be able to push the build to Chocolatey.

Full Changelog: 5.0.12...5.0.14

5.0.12

This release will not be published to Chocolatey due to a technical issue. We have found the root cause and the next release will most likely be published there.

Thank you @adwitkow for the fix to a nasty issue in the 5.0.10 release.

Full Changelog: 5.0.10...5.0.12

5.0.10

What's Changed

We have have changed the build system to use GitHub Actions. This is the first release using that. Unfortunately there is an issue with publishing to Chocolatey. This is being investigated.

We have also changed from GitFlow to Release Flow so PRs should be made against the master branch from now on.

Full Changelog: 5.0.7...5.0.10

5.0.7

Fixes the issue with the bad zip file that was introduced in version 5.0.5.

ServiceBus Explorer build 5.0.7-ci.2.build.937.

Changes: https://github.com/paolosalvatori/ServiceBusExplorer/milestone/24?closed=1

5.0.5

ServiceBus Explorer build 5.0.5-ci.40.build.930.

IMPORTANT: there's an issue with the packaged binaries. Follow the workaround until it's resolved in 5.0.7.

Changes: https://github.com/paolosalvatori/ServiceBusExplorer/milestone/22?closed=1

5.0.4

ServiceBus Explorer build 5.0.4-ci.19.build.853.

• #560 Cannot save entity specific connection string
• #547 Value cannot be null when re-submitting multiple messages at once (batch)
• #551 Tab order in 'Enter Topic Filter Expression' is out of order
• #554 Purge messages in queue not working in 5.0.3
• #548 "field must be a number" when creating queue/topic entity
• #545 Regression on session-enabled queue message retrieval

5.0.3

This release contains a bug that occurs when purging messages. Instead of the normal messages being purged, the dead-lettered messages get purged.

ServiceBus Explorer build 5.0.3-ci.1.build.837.

5.0.2

ServiceBus Explorer build 5.0.2-ci.19.build.800.

Warning: This release contains a bug that occurs when purging dead-lettered messages. Instead of the deadlettered messages being purged, the normal messages get purged.

The Chocolatey package was not approved for this and the previous release due to a changed icon file causing the Chocolatey Icon URL check to fail. However, it is still possible to use the package.

If you are connecting to Azure Service Bus without using a proxy but have outgoing ports closed in a firewall you need to open additional ports for this release. The ports are 5671 and 5672.

If you are connecting to Azure Service Bus through a proxy there is a new setting, Use AmqpwebSockets, which must be enabled in that case.

• Regression: cannot resubmit a message
• ListenerControl.cs: Fix typo in log message
• Premium ServiceBus - Create Queue/Topic with max Queue Size - 80GB
• Resubmitting message with changed message body
• Upgraded Event hubs SDK
• UI refactorings & enhancements
• Fix coloring of subscription nodes
• Prevent tab to switch after receiving messages

Full list

5.0.1

Warning: Repair and resubmit message does not work properly in this version. It will ignore any changes done to the message and just send the original message. This issue is fixed in the develop branch.

If you are connecting to Azure Service Bus without using a proxy but have outgoing ports closed by default you need to open additional ports for this release. The ports are 5671 and 5672.

If you are connecting to Azure Service Bus through a proxy there is a new setting, Use AmqpwebSockets, which must be enabled in that case.

The technical reason for this is that version 5.0.1 uses the Track 1 (Microsoft.Azure.ServiceBus/Microsoft.Azure.ServiceBus (.NET Standard)) SDK in addition to the Track 0/WindowsAzure.ServiceBus/Microsoft.ServiceBus.Messaging (.NET Framework)) SDK. The Track 1 SDK uses AMQP for communicating with the Service Bus service. Unless you change the TransportType to AmqpwebSockets it will use ports 5671 and 5672. The Track 0 SDK uses ports 9350 - 9354 by default.

By using the Track 1 SDK the NET Framework version had to be increased from 4.6.1 to 4.6.2. There are many more dlls that needs to be included since the Track 1 SDK is built on .NET Standard.

For more information about Service Bus SDK versions see this blog post. For more information about firewall port openings for Service Bus check out this article.

• Fix copying behavior of properties when resubmitting messages
• When resubmitting one or more messages from the deadletter subqueue the deadletter properties are kept
• Retiring support for Windows Server Service Bus
• fixed cloning by utilizing Service Bus .Clone(stream) instead of .Clone(string)
• Feature Request: Add Queue Listener for specific Message Session
• Emphasise how to delete message custom property
• Added label about the delete key
• Remove support for ACS
• Removed support for ACS authentication
• Add coloring feature to nodes
• Allow selection of message counts to display
• The default values for server and receive timeout should be increased
• Added UI flow to reduce the likelihood of accidental mass deletions
• Enable configuring proxy configuration from the Options dialog
• Allow updating saved service bus namespaces
• Add proxy configuration UI and logic
• Put tabs on the Options dialog
• Closing the RepairAndResubmit message dialog used to reload all topics and queue
• Change Options form buttons
• Commandlineoptions
• Import Topic with CorrelationId Rules throws exception
• Persist Message Content Type in the settings
• Enhance forwards UI experience
• Refresh subscription does not clear previously deleted rules
• Refresh subscription does not clear previously deleted rules
• Splitted it into smaller assemblies and add support for the new SDKs
• Save message body as file
• Prevent using an entity-specific connection string
• Add autoindent check control to MessageForm #195
• Prepend sb:// to endpoint if not present
• Add "from sequence number" text box.
• Version checker
• Ability to filter queue and subscription messages
• Make reversion from User config file to Application config file stick
• Change “Ok” to “OK” in button text
• Checking if field is already a timespan
• Fix long delay when creating invalid entity
• Deadletter messages panel not showing system properties of a message.
• Reduce excess precision in msg/sec rates in log messages

4.1.112

This release contains the following improvements and fixes:

• Added support for OR logic in Queue and Topic filters (#268)
• GUI change for submitting messages in batch mode (#297)
• Add support for SendDisabled and ReceiveDisabled states for Queues
• TimeSpan support for Custom Properties
• Lazy load subscription rules (#308)
• Fix bug when body is empty or null (#310)

It is planned to put this version in the Microsoft Store in a few weeks.