http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660You should stop relying in ObjectDisposedException and not touch an object after disposing it. Think of ObjectDisposedException as a debuging aide. http://ayende.com/3835/and-now-what#comment13http://ayende.com/3835/and-now-what#comment13Tue, 03 Feb 2009 17:52:59 GMTThough context is and always would be helpful (or at least more informative ;) ) I'm with Oren on this one. NRE == bug. http://ayende.com/3835/and-now-what#comment12http://ayende.com/3835/and-now-what#comment12Tue, 27 Jan 2009 23:58:38 GMT@Mr Anonymous Hey no fair - you stole my handle. http://ayende.com/3835/and-now-what#comment11http://ayende.com/3835/and-now-what#comment11Tue, 27 Jan 2009 22:11:25 GMT*choke* JMS.... :-P http://ayende.com/3835/and-now-what#comment10http://ayende.com/3835/and-now-what#comment10Tue, 27 Jan 2009 22:05:15 GMTNo, that is actually not an assert that is failing. The assert is in my code. The problem is that NRE. http://ayende.com/3835/and-now-what#comment9http://ayende.com/3835/and-now-what#comment9Tue, 27 Jan 2009 20:24:34 GMT@Ayende Thanks for the clarification. I didn't doubt that it was a bug on their part, I just like seeing what caused them so that I know in the future where the dragons may be. http://ayende.com/3835/and-now-what#comment8http://ayende.com/3835/and-now-what#comment8Tue, 27 Jan 2009 20:22:00 GMTAn assert failing in production code means that some invariant somewhere is no longer true, and that the author of the code considered such a situation a bug. Therefore Oren's statement is valid. http://ayende.com/3835/and-now-what#comment7http://ayende.com/3835/and-now-what#comment7Tue, 27 Jan 2009 20:21:32 GMTJustin, Null Reference is almost always a bug. In this case, I am access the AppSpecific property on a message, and it throws this error. This is caused because of a bug in certain scenarios in which even though the queue is set to accept AppSpecific, it doesn't http://ayende.com/3835/and-now-what#comment6http://ayende.com/3835/and-now-what#comment6Tue, 27 Jan 2009 20:16:44 GMTIf you are going to make a statement like this, then shouldn't you at least show the situation under which the error occurred? From what you have shown us, it is hard to ascertain if your claims are indeed true, or you are doing something wrong and just blaming it on the .net MSMQ apis. http://ayende.com/3835/and-now-what#comment5http://ayende.com/3835/and-now-what#comment5Tue, 27 Jan 2009 20:03:22 GMTshawn, No, I am using the delegate passed to the async method http://ayende.com/3835/and-now-what#comment4http://ayende.com/3835/and-now-what#comment4Tue, 27 Jan 2009 19:12:05 GMTare you using PeekCompleted? i use this pattern for peeks and reads and it may be why i haven't encountered the set of problems you have. [msdn.microsoft.com/.../...queue.peekcompleted.aspx](http://msdn.microsoft.com/en-us/library/system.messaging.messagequeue.peekcompleted.aspx)http://ayende.com/3835/and-now-what#comment3http://ayende.com/3835/and-now-what#comment3Tue, 27 Jan 2009 18:55:59 GMT@J - haha - second that! http://ayende.com/3835/and-now-what#comment2http://ayende.com/3835/and-now-what#comment2Tue, 27 Jan 2009 18:43:26 GMThave you ever thought about joining Microsoft as a tester? :) http://ayende.com/3835/and-now-what#comment1http://ayende.com/3835/and-now-what#comment1Tue, 27 Jan 2009 18:08:02 GMT