Message contracts can be defined using plain classes or interfaces. For NServiceBus to find those classes when scanning assemblies they need to be marked with the
IMessage interface, which essentially says, "this is a message definition". This allows decoupling message contracts from the NServiceBus assembly.
This dependency can cause problems when there are different services that run different versions of NServiceBus. Jonathan Oliver has a great write up on this very subject.
This is not a big deal for commands because they are always used with in the boundary of a single service and it's fair to require a service to use the same version of NServiceBus. But when it comes to events, this becomes more of a problem since it requires the services to all use the same version of NServiceBus, thereby forcing them to upgrade NServiceBus all at once.
There are a couple of ways this can be solved.
- NServiceBus follows the semver.org semantics, only changing the assembly version when changes are not backward compatible or introduce substantial new functionality or improvements. This mean that Version 3.0.1 and Version 3.0.X have the same assembly version (3.0.0), and file version of course changes for every release/build. This means that as long as NuGet updates are done with the -safe flag the service contracts will stay compatible.
- Support for running in "Unobtrusive" mode means no reference to any NServiceBus assemblies is required from message assemblies, thereby removing the problem altogether.
NServiceBus allows defining custom message conventions instead of using the
IEvent interfaces and attributes like
ExpressAttribute. NServiceBus also supports conventions for encrypted properties, express messages, databus properties and time to be received. With these conventions combined a reference to NServiceBus can be avoid.
StartsWith, then a null check should be used. So include
.Namespace != nullat the start of the convention. Otherwise a null reference exception will occur during the type scanning.