http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Oh, here's the URL for my project: [http://code.msdn.microsoft.com/duratrans](http://code.msdn.microsoft.com/duratrans) http://ayende.com/3790/msmq-and-troublesome-api-experience#comment5http://ayende.com/3790/msmq-and-troublesome-api-experience#comment5Wed, 25 Feb 2009 19:16:27 GMTMSMQ and transactions wasn't something to look forward to when coding, and then WCF came along and takes the pain out of it. I had a lot of fun making this little project. The transactions make MSMQ behave in a way that proves to be super useful. It's very durable to, you can turn the services on and off as you like, and when they come back on-line things keep processing. If anything goes wrong, the transaction blows up and keeps the message on the queue to be processed again. It's very hard for this system to fail to process the initial request (and there's contingency rules built in to decide when it's had enough). I see this from a different angle, I've got to say using the WCF MSMQ transport removes overhead and complexity. http://ayende.com/3790/msmq-and-troublesome-api-experience#comment4http://ayende.com/3790/msmq-and-troublesome-api-experience#comment4Wed, 25 Feb 2009 19:15:08 GMTUsing the WCF msmq transport only add overhead & complexity that aren't really needed. http://ayende.com/3790/msmq-and-troublesome-api-experience#comment3http://ayende.com/3790/msmq-and-troublesome-api-experience#comment3Sun, 04 Jan 2009 00:25:33 GMTthere are a number of things with system.messaging that bug me, but that's definitely one of them. the api explosion around reading messages is a real headache as well. another thing that gets to me is the need to set "this property is readable" properties before you inspect certain attributes of your queue or message. while i understand the need to do this, the way it's done is suboptimal to say the least. have you looked at using WCF's msmq transport rather than system.messaging for raw msmq work? http://ayende.com/3790/msmq-and-troublesome-api-experience#comment2http://ayende.com/3790/msmq-and-troublesome-api-experience#comment2Sat, 03 Jan 2009 23:22:15 GMTMan, this is an ENTERPRISE api (in some Microsofty way) http://ayende.com/3790/msmq-and-troublesome-api-experience#comment1http://ayende.com/3790/msmq-and-troublesome-api-experience#comment1Sat, 03 Jan 2009 15:50:16 GMT