The AzureServiceBus transport is now a feature. This means that it now can
be used from a on-premise windows host.
Azure storage queue transport is now a feature
The azure service bus transport now supports the NServiceBus/Transport
connection string as well
Fixed a failing unit test that checked that msmq is the default transport
if no explicit transport is selected
refactored azure servicebus naming conventions for topics and subscriptions to be more easily overridable, stupid 50 character limit!
Merge branch 'develop' of https://github.com/NServiceBus/NServiceBus into develop
Removed return otherwise the service is not installed.
Internal conventions need to be public otherwise users can't query sagas, closes #1171
fixed spelling mistake
Removed the use of .Sagas() since it's obsoleted
fixing some issues with azure hosting after feature refactoring
Merge branch 'develop' of https://github.com/NServiceBus/NServiceBus into develop
fixed default transport issue
updated azure storage queue samples
Updating readme with the RavenDB license
Made sure that we run the basic send receive test for all builders
Introducing a way to change scale out behaviour of endpoints when using a
broker based transport. Frontends and other endpoints that want to make
use of callback can now make sure that they get a unique inout queue when
scaled out in order to not miss callback messages
RabbitMQ now honor the scalout directives for central of unique queue per
endpoint
The ActiveMQ transport now honor the settings for unique or centralized
input queue when scaling oout endpoints
azure topic publisher name initialized a bit later