This will document my “dummy” experience. I’ve been using NServiceBus for a while, but the license model changed out from under us so we’ve been investigating alternatives. A fellow in the office pointed us to Rhino ESB (he had pointed us to NServiceBus earlier).
- SNAP – I need to get GIT running in the desktop (git v220.127.116.11)
- Brought up a new command window and typed:
- git clone https://github.com/ayende/rhino-esb.git
- Had to figure out how to use psake
So, that appears to be all there is to it.C:\Source\external\rhino-esb>powershell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\Source\external\rhino-esb> .\psake.ps1 .\default.ps1
- We’ve been making extensive use of Autofac as our container and Rhino has a predisposition for Castle Windsor. We’ll just use Windsor in the handlers for now and leave other areas (i.e. ASP.NET MVC 2) to use Autofac. I’m told that a container agnostic version of Rhino ESB is in the works.
- Testing with NServiceBus was pretty straightforward as it provided mocks of our handlers and also setup the expect portions. I’m told that with Rhino Mocks we don’t need to worry about that and we just test our handler’s independently from the ‘service bus’.
- No more need to adorn our message classes with IMessage.