You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 30, 2019. It is now read-only.
For the MSMQ transport, there is the "NServiceBus.Utils.MsmqUtilities.CreateQueueIfNecessary()" function to easily create additional queues if required. Such a scenario is when you are writing an NSB satellite that needs its own queue associated with the endpoint (usually seen when implementing "INeedToInstallSomething").
There is the "WindowsServicebusQueueClientCreator" class for Windows Service Bus transport but it's not super usable.
The text was updated successfully, but these errors were encountered:
You are correct, queue are created automatically, that is why I do not understand why audit and errors queue in some scenario do not follow this behavior.
I’m facing the exact same problem, currently investigating.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For the MSMQ transport, there is the "NServiceBus.Utils.MsmqUtilities.CreateQueueIfNecessary()" function to easily create additional queues if required. Such a scenario is when you are writing an NSB satellite that needs its own queue associated with the endpoint (usually seen when implementing "INeedToInstallSomething").
There is the "WindowsServicebusQueueClientCreator" class for Windows Service Bus transport but it's not super usable.
The text was updated successfully, but these errors were encountered: