Getting Started
Architecture
NServiceBus
Transports
Persistence
ServiceInsight
ServicePulse
ServiceControl
Monitoring
Samples

Side-by-side with legacy Azure Service Bus

If it's necessary to run an endpoint instance using the Azure Service Bus transport and an endpoint instance using the legacy Azure Service Bus transport in the same process and AppDomain, there is the risk of name collision between types from the two transports.

To avoid name clashes, use aliases to reference types of one of the transports. For example, to define an alias for the legacy Azure Service Bus transport, add the following snippet to the project file:

<Target Name="ChangeAliasesOfNugetRefs" BeforeTargets="FindReferenceAssembliesForReferences;ResolveReferences">
  <ItemGroup>
    <ReferencePath Condition="'%(FileName)' == 'NServiceBus.Azure.Transports.WindowsAzureServiceBus'">
      <Aliases>LegacyASB</Aliases>
    </ReferencePath>
  </ItemGroup>
</Target>

Once the alias is defined, reference the alias in the C# source files where it is needed by adding it to the usings list:

extern alias LegacyASB;

The alias can now be used to reference types from the Azure Service Bus transport assembly:

#pragma warning disable 618
        var legacyASB = configurationASB.UseTransport<LegacyASB::NServiceBus.AzureServiceBusTransport>();
#pragma warning restore 618

Related Articles


Last modified