This post originated from an RSS feed registered with .NET Buzz by Jeff Key. Original Post: Get your hands off my queue Feed Title: Jeff Key Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/jkey/Rss.aspx Feed Description: Topics revolve around .NET and the Windows platform. Latest .NET Buzz Posts Latest .NET Buzz Posts by Jeff Key Latest Posts From Jeff Key

Need exclusive read access to an MSMQ queue? .NET gives you an easy way to do this, but a not-so-obvious way to give up the queue. To obtain a “read lock“ on the queue, simply set MessageQueue.DenySharedReceive to true. From the docs:

DenySharedReceive specifies the shared mode of the queue referenced by this MessageQueue. Set DenySharedReceive to true to indicate that only this MessageQueue should have access to peek or receive messages from the queue with the specified Path. If another MessageQueue or another application is associated with the same queue resource, that instance or application will not be able to peek or receive messages, but it can still send them.

If DenySharedReceive is false, the queue is available to multiple applications for sending, peeking, or receiving messages.

Unfortunately, simply setting DenySharedReceive to false didn't allow others to read from the queue. I had to unsubscribe from ReceiveCompleted and close the queue. YMMV.