1.2.0
As part of this release we had 20 commits which resulted in 3 issues being closed.
Features
#15 Support for sending to queues in different databases
When sending a message the MessageSender will check if a specific connectionstring is defined for this queue. If that is the case, the other connectionstring will be used.
The extra connectionstrings can be configured in the web.config like this:
<connectionStrings>
<add name="NServiceBus/Transport" connectionString="Data Source=.;Initial Catalog=DBForReceiveQueue; Integrated Security=True" />
<add name="NServiceBus/Transport/Queue1Name" connectionString="Data Source=.;Initial Catalog=DBForQueue1; Integrated Security=True" />
<add name="NServiceBus/Transport/Queue2Name" connectionString="Data Source=.;Initial Catalog=DBForQueue2; Integrated Security=True" />
</connectionStrings>
Content trimmed. See full issue
Bugs
#17 HasActiveTransaction in UnitOfWork class returns true even if the transaction for the current thread has been cleared
The use of IsValueCreated is incorrect, because it will return true regardless if the value is null or not.
public bool HasActiveTransaction()
{
return currentTransaction.IsValueCreated;
}
The believe the method should check for null values.
public bool HasActiveTransaction()
Content trimmed. See full issue
Where to get it
You can download this release from:
- Or nuget