Contents

• Getting Started
•     Overview
•     Architectural Principles
•     Transactions

• Samples
•     Web App Integration
•     Web App - Asp.Net Mvc3 Integration
•     Encryption
•     Full Duplex - Request/Response
•     Generic Host - Logging
•     PubSub
•     Versioning
•     Message Mutators
•     Unobtrusive
•     Data Bus
•     Scale Out

• Day to Day
•     Dependency Injection
•     Support for child containers
•     Logging
•     Messages as Interfaces
•     Introducing IEvent and ICommand
•     Unobtrusive mode messages
•     Unit Testing
•     One way/Send only endpoints

• Hosting
•     In Your Process
•     NServiceBus Host
•         Profiles
•     32-bit (x86) Host Process

• Management and Monitoring
•     Auditing
•     Monitoring
•     Msmq Information

• Scaling Out
•     Performance Information
•     Multi-Site with the Gateway
•         More about the Gateway
•     Multi-Server with the Distributor
•     Unit of work in NServiceBus 3.0
•         Unit Of Work implementation for RavenDB

• Publish-Subscribe
•     Overview
•     API and Configuration

• Long-Running Processes
•     Sagas

• Customization
•     Customizing Configuration

Msmq Information

The default transport used by NServiceBus is MSMQ.
This page holds information about MSMQ relevant to NServiceBus.

History

MSMQ stands for Microsoft Message Queuing and is available on almost all Windows machines
from Windows 2000 onwards (though not including Win2K home edition).
With Windows XP and Server 2003 Microsoft introduced MSMQ 3.0, and Service Pack 2 brought MSMQ to version 3.1, with an enterprise ready feature set.

During the time that the Connected Systems Division at Microsoft was developing Indigo (now known as WCF), there was the intention to replace MSMQ with something new. 2 years later, the effort to replace MSMQ was abandoned and MSMQ was integrated into the standard WCF model and configuration.

Other technologies like BizTalk and SQL Server Service Broker still do not have a .NET API in the Base Class Library (BCL). Included in the Vista release, MSMQ 4.0 was made available showing Microsoft's continued commitment to it. To this day, MSMQ remains the primary durable communications technology on the Microsoft platform.

Virtual Private Networks (VPN)

MSMQ isn't smart enough to dynamically detect network interfaces. Therefore if you connect a VPN after the MSMQ service is started, you have to restart the MSMQ service for it to detect the VPN. Once it's started with the interface the VPN is free to disconnect/reconnect whenever it wants.

It is recommended to have setup batch scripts that run on server startups to connect the VPN which then restart the MSMQ service automatically.

Microsoft Links

MSMQ Forums

MSMQ on Windows Server 2003

MSMQ on Windows Server 2008