Messaging through a service bus in .NET using MassTransit part 4: dependency injection with StructureMap


In the previous post we saw how to publish messages with MassTransit. Our demo register customer command listener publishes a customer registered event that any interested party can sign up to. An advantage with the setup is that the publisher has no knowledge of the consumers, they are completely decoupled. The opposite and more frequent case is often a manager application that knows exactly which parties should be notified and sends them a message directly.

In this post we’ll diverge a little from messaging techniques and look at dependency injection instead. We’re inte particular interested in how to inject a dependency into a registered command or event consumer.

Never heard of dependency injection?

If you are working with relatively advanced topics such as a .NET service bus then I assume that you have also at least come across terms like dependency injection, inversion of control or dependency inversion. They are often used to mean the same thing: a class which depends on another class or interface to perform its functions should be supplied that dependency by the caller. This often manifests itself in constructors which inform the callers what dependencies they need. Dependency injection is not some fancy C# language construct. The challenging part is most often to identify the tightly coupled dependencies and factor them out into separate and independent pieces.

The following is an example of a constructor injection, i.e. where a class indicates its “needs” via the constructor. This is by far the most common form of dependency injection:

public class PublicMessage
	private readonly IMessageCollector _messageCollector;
	private readonly ITextWriter _textWriter;

	public PublicMessage(IMessageCollector messageCollector, ITextWriter textWriter)
		if (messageCollector == null) throw new ArgumentNullException("Message collector");
		if (textWriter == null) throw new ArgumentNullException("Text writer");
		_messageCollector = messageCollector;
		_textWriter = textWriter;

	public void Shout()
		string message = _messageCollector.CollectMessageFromUser();

There’s a number of posts on this blog dedicated to dependency injection. Go ahead and read them if you want to refresh your memory:

A dependency in the RegisterCustomerConsumer

Currently our RegisterCustomerConsumer only has an empty constructor. It has no external dependencies since it doesn’t carry out much work anyway other than printing a couple of messages. Mind you the Console.WriteLine calls could be abstracted away into some interface like IMessageWriter so that callers can control where the messages are printed. So we can identify a dependency even in this simple class.

We’ll do something different but the solution presented here is the same. We want to add a repository that the RegisterCustomerConsumer can delegate the save procedure to. Add a new C# class library called MyCompany.Domains with the following domain and a matching repository interface:

using System;

namespace MyCompany.Domains
	public class Customer
		private readonly Guid _id;
		private readonly string _name;
		private readonly string _address;

		public Customer(Guid id, string name, string address)
			_id = id;
			_name = name;
			_address = address;
		public Guid Id { get { return _id; } }
		public string Address { get { return _address; } }
		public string Name { get { return _name; } }
		public DateTime RegisteredUtc { get; set; }
		public int Type { get; set; }		
		public bool Preferred { get; set; }
		public decimal DefaultDiscount { get; set; }
namespace MyCompany.Domains
	public interface ICustomerRepository
		void Save(Customer customer);

Add a project reference to MyCompany.Domains from MassTransit.Receiver.

Here’s the updated RegisterCustomerConsumer class with an extended constructor:

using MyCompany.Domains;
using MyCompany.Messaging;
using System;
using System.Threading.Tasks;

namespace MassTransit.Receiver
	public class RegisterCustomerConsumer : IConsumer<IRegisterCustomer>
		private readonly ICustomerRepository _customerRepository;

		public RegisterCustomerConsumer(ICustomerRepository customerRepository)
			if (customerRepository == null) throw new ArgumentNullException("Customer repository");
			_customerRepository = customerRepository;
		public Task Consume(ConsumeContext<IRegisterCustomer> context)
			IRegisterCustomer newCustomer = context.Message;
			Console.WriteLine("A new customer has signed up, it's time to register it in the command receiver. Details: ");

			_customerRepository.Save(new Customer(newCustomer.Id, newCustomer.Name, newCustomer.Address)
				DefaultDiscount = newCustomer.DefaultDiscount,
				Preferred = newCustomer.Preferred,
				RegisteredUtc = newCustomer.RegisteredUtc,
				Type = newCustomer.Type

				Address = newCustomer.Address,
				Id = newCustomer.Id,				
				RegisteredUtc = newCustomer.RegisteredUtc,
				Name = newCustomer.Name				

			return Task.FromResult(context.Message);

We add the dependency through the constructor and call the Save method in the Consume function, there’s nothing magic in that. However, you’ll see that Visual Studio shows a compilaton error:

‘RegisterCustomerConsumer’ must be a non-abstract type with a public parameterless constructor in order to use it as parameter ‘TConsumer’ in the generic type or method ‘ConsumerExtensions.Consumer(IReceiveEndpointConfigurator, Action<IConsumerConfigurator>)’

Unfortunately we cannot just supply a concrete implementation of the interface like that.

The concrete repository

Before we continue let’s just implement the ICustomerRepository interface. Add a new C# class library called MyCompany.Repository.Dummy with the following implementation:

using MyCompany.Domains;
using System;

namespace MyCompany.Repository.Dummy
	public class CustomerRepository : ICustomerRepository
		public void Save(Customer customer)
			Console.WriteLine(string.Concat("The concrete customer repository was called for customer ", customer.Name));

StructureMap IoC

We’ll have to use an inversion-of-control container here. MassTransit supports a number of IoC containers including Ninject, Unity, Autofac, Castle Windsor and StructureMap. I’m most familiar with StructureMap so I’ll use that in this example. I have used the code example on the relevant MassTransit documentation page as a starting point, but the code code presented below is slightly different.

Add the following NuGet package to MassTransit.Receiver:


This library will add a number of extension methods to MassTransit. Here’s the updated Program.cs of MassTransit.Receiver:

using MassTransit.RabbitMqTransport;
using MyCompany.Domains;
using MyCompany.Repository.Dummy;
using StructureMap;
using System;

namespace MassTransit.Receiver
	class Program
		static void Main(string[] args)
			Console.Title = "This is the customer registration command receiver.";
		private static void RunMassTransitReceiverWithRabbit()
			var container = new Container(conf =>
			string whatDoIHave = container.WhatDoIHave();

			IBusControl rabbitBusControl = Bus.Factory.CreateUsingRabbitMq(rabbit =>
				IRabbitMqHost rabbitMqHost = rabbit.Host(new Uri("rabbitmq://localhost:5672/accounting"), settings =>

				rabbit.ReceiveEndpoint(rabbitMqHost, "", conf =>


For the above code to compile we have to add a project reference to MyCompany.Repository.Dummy from MassTransit.Receiver.

At the start of RunMassTransitReceiverWithRabbit we configure the StrutureMap container. We declare which concrete implementations we want to use. We only have one so we tell StructureMap to construct a CustomerRepository if it finds a dependency on ICustomerRepository. The call to WhatDoIHave is not necessary for the code to work. I only wanted to show that as a tip. The function returns a string in tabular format showing which abstractions and concrete implementations it has in its registry. Take a look at the string and you’ll find the ICustomerRepository/CustomerRepository pair.

Later on we send in the container to the Consumer method where we register RegisterCustomerConsumer. That’s the same function we saw before but the overload where a StructureMap container could be passed in is new. Before the NuGet package was added there were 3 overloads of Consumer, now there’s a fourth one.

That’s it, you can run the demo the same way as in the previous post. You can set a breakpoint within RegisterCustomerConsumer to check whether ICustomerRepository repository was correctly resolved. Start the receivers first and then the publisher. You’ll see that the system works like before and that ICustomerRepository was correctly resolved to a CustomerRepository. There will be an extra message in the MassTransit.Receiver command window:

“The concrete customer repository was called for customer Nice people LTD”

So we have successfully added a dependency to the RegisterCustomerConsumer class. To be honest I would have been happier to get this done without an IoC container since dependency injection should not depend on such a mechanism in a simple project such as a console application. However, I didn’t find any other way to inject a dependency into the consumer class. If you know a better way then let everyone know in the comments section.

We’ll continue in the next post.

View the list of posts on Messaging here.


About Andras Nemes
I'm a .NET/Java developer living and working in Stockholm, Sweden.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s


A great site

Elliot Balynn's Blog

A directory of wonderful thoughts

Robin Sedlaczek's Blog

Developer on Microsoft Technologies

HarsH ReaLiTy

A Good Blog is Hard to Find

Softwarearchitektur in der Praxis

Wissenswertes zu Webentwicklung, Domain-Driven Design und Microservices

the software architecture

thoughts, ideas, diagrams,enterprise code, design pattern , solution designs

Technology Talks

on Microsoft technologies, Web, Android and others

Software Engineering

Web development

Disparate Opinions

Various tidbits

chsakell's Blog

Anything around ASP.NET MVC,WEB API, WCF, Entity Framework & AngularJS

Cyber Matters

Bite-size insight on Cyber Security for the not too technical.

Guru N Guns's

OneSolution To dOTnET.

Johnny Zraiby

Measuring programming progress by lines of code is like measuring aircraft building progress by weight.

%d bloggers like this: