2009/1/8 Aidan Skinner <[email protected]>: > I think System.Messaging is probably more relevant to .Net, this is > the route that Mono has gone down with ActiveMQ and RabbitMQ: > http://www.mono-project.com/SystemMessaging (there was also an attempt > to implement it on top of our 0-8 client but that didn't work out).
My experience has been that WCF is key for new .NET development. I have recently worked on a project that used WCF with IBM MQ, along with CXF (this was using SOAP over messaging). That's not to say System.Messaging is not desirable, but the WCF for IBM MQ saved us a lot of time and effort. RG
