When the endpoints use different database as specified in the connection string, Bus.Reply is not routed properly

[indualagarsamy]

When endpoints are configured to be in different databases and the connection strings are properly specified in the app.config for the endpoints, Bus.Reply is being attempted to be sent to the wrong address and fails to be sent.

Who is affected

Any endpoint running on SQLServer transport that is calling Bus.Reply() and using multi-database support via app.config connection string convention.

Problem

The connection string convention is, NServiceBus/Transport/EndpointName.

However, when using the Bus.Reply, the callback address is being used to determine the connection string and therefore fails.

When attempting to route the reply message, the address is correctly determined as:
https://github.com/Particular/NServiceBus.SqlServer/blob/master/src/NServiceBus.SqlServer/SqlServerMessageSender.cs#L41

However, instead of using the Callback address to find the connection string, the endpoint (contained in sendOptions.Destination.Queue must instead be used.
https://github.com/Particular/NServiceBus.SqlServer/blob/master/src/NServiceBus.SqlServer/SqlServerMessageSender.cs#L54

Relates to Feature: #15

[johnsimons]

@indualagarsamy any chance you can add a failing acceptance test for this ?

[indualagarsamy]

@johnsimons - I am looking to see if we have any acceptance tests for this feature. That was my next step.

[indualagarsamy]

@andreasohlund @johnsimons - does the fix look right to you?