Skip to content
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Example code for extending the behaviour of MSMQ Inspector.

We do make the bold assumption that you have a copy of the software installed (version of at least - see and have MSMQ configured on the development machine.

Plugin use is restricted to the Premium licensed users.

For a more complete tutorial - see MSMQ.ReportGenerator.PlugIn Read Me

The current example is a plug-in that adds a custom message deserialiser (or message decoder).

Key things to keep in mind:

  • Target .NET version 4
  • The DLL must be 32 Bit
  • It needs to be signed
  • The filename by default should be "*.Plugin.dll" (this is what the application looks for at startup)

The example was coded and tested using Visual Studio 2013, Xamarin Studio and SharpDevelop.

See the code comments for more detail.

  • The ExampleXmlMessageDecoderLoader gets called during start up - this is where you register services etc
  • The ExampleXmlMessageDecoder does the work
  • The ExampleXmlMessageDecoderTests just inject an XML stream as an example

Installing a Plug-in

The application will search for plug-ins (*.plug-in.dll) in:

  • The current program folder (e.g. C:\Program Files (x86)\MSMQ Inspector or the development folder)
  • The common data path in the directory C:\ProgramData\MSMQInspector
  • The local data path in the directory C:\Users\(*username*)\AppData\Local\MSMQInspector

A binding redirect is used to ensure that plug-ins build against an older assembly still load on newer versions.


If you have a particular scenario you would like to implement, please Contact Us with some details.

There may be existing pieces you can plug together or a simple kick-start on where to look.


Example code for extending the behaviour of MSMQ Inspector.



No releases published


No packages published
You can’t perform that action at this time.