FAQ Contents

• MsmqTransportConfig
• Defining a message
• Store & forward for a message
• Discarding old messages
• Instantiating a message
• Send a message
• Set message destination
• Messages and queues
• Handling messages
• Message handler ordering
• Referencing IBus in a handler
• Technical message information
• Replying to messages
• Handling responses
• Publish Subscribe
• Exception handling
• Exposing web/wcf services
• Type not registered in serializer
• Insufficient resources to perform operation
• How to specify your input queue name
• What happens when a worker goes down?
• RunMeFirst.bat throws an exception

How do I define a message?

public class MyMessage : IMessage { }

OR

public interface IMyMessage : IMessage { }

One of the advantages of using interfaces to define messages instead of classes is that you get "multiple inheritance" - one message can extend multiple other messages.

This is useful for solving a specific class of versioning problems.

Say that your business logic represents a state machine with states X and Y. When your system gets into state X, it publishes a message - EnteredStateX. When your system gets into state Y, it publishes a message - EnteredStateY. (For more information on how to publish a message, see below)

In the next version of your system, you add a new state Z, which represents the co-existence of both X and Y. So, you define a message EnteredStateZ which inherits both EnteredStateX and EnteredStateY.

When your system publishes EnteredStateZ, clients subscribed to either (or both) EnteredStateX or EnteredStateY will be notified.

Without the ability to have a message extend multiple others, you'd have to use composition. This would prevent the infrastructure from knowing how to automatically route messages to pre-existing subscribers of the composed messages.