ASQ v7: API for secure connection string with default connection string only is broken

[SeanFeldman]

Who's affected

• Anyone using NServiceBus version 7 and above

Symptoms

When using ASQ with secured connection string (alias instead of connection string) with a default storage account, dispatches are failing with NullReferenceException.

Details

Default storage account connection string is not associated with the default alias. Instead, the alias is mapped to an empty string, which causes CreateQueueClients to build a null CloudQueueClient that is used during dispatching, causing an exception.

According to documentation, API should be used in the following manner:

var transport = endpointConfiguration.UseTransport<AzureStorageQueueTransport>();
transport.ConnectionString("account_A_connection_string");
transport.UseAccountAliasesInsteadOfConnectionStrings();
transport.DefaultAccountAlias("account_A");

In reality this is failing when an attempt is made to dispatch a message to account_A.

Workaround

Workaround is to register default connection string and its alias via AccountRouting() API.

var transport = endpointConfiguration.UseTransport<AzureStorageQueueTransport>();
transport.ConnectionString("account_A_connection_string");
transport.UseAccountAliasesInsteadOfConnectionStrings();
transport.DefaultAccountAlias("account_A");
//workaround - force alias registration
transport.AccountRouting().AddAccount("account_A", "account_A_connection_string"); 

Affected versions

• 7.4.x
• 7.5.x
• 8.0

[SeanFeldman]

Documentation update is needed and then this issue could be closed.

[SeanFeldman]

Closing in favour of documentation PR Particular/docs.particular.net#3595