2.0.0

NServiceBus 7 supports .NET Core 2.0, enabling cross-platform development and deployment plus hosting on Linux and in Docker containers, while still fully supporting Windows and the .NET Framework.

NServiceBus.FileBasedRouting 2.0.0 is required when upgrading to NServiceBus 7.

Find out more about NServiceBus 7's new features.

Upgrading from earlier versions?

Take a look at the NServiceBus 6 to 7 upgrade guide.

Want to see all the changes?

They are all on the 2.0.0 milestone.

What are the API breaking changes?

Take a look at a report of API changes between versions.

1.2.1

Fixed bugs

• #386 Endpoint crashes when assembly is not found
• #386 Endpoint crashes when rereading an invalid XML

1.2.0

Features

• Make refresh interval configurable
  By default, NServiceBus.FileBasedRouting tries to reload the routing file every 30 seconds. This value can now be changed by passing an additional TimeSpan parameter to UseFileBasedRouting. If the file should only be read once at endpoint startup time, pass TimeSpan.Zero.

Fixed bugs

• Endpoint crashes if a type can not be found
  Endpoints using NServiceBus.FileBasedRouting could crash on the attempt to load a message type which doesn't exist. This could be caused by typos in the type definition or if the assembly, containing the type isn't available to the endpoint trying to parse the routing file.

1.1.0

NServiceBus.FileBasedRouting 1.1.0 supports loading the routing file from a Uri. A Uri can be configured instead of a file path:

e.g. transport.Routing().UseFileBasedRouting(new Uri("https://your-server.com/endpoints.xml"));

This new feature allows to share the routing file on a large set of hosting options.

Issues assigned to this release