http://blogs.msdn.com/b/junfeng/archive/2007/07/30/lock-object-and-threadabortexception.aspxWe have experience some weird deadlock using managed code. We have a class with some shared resources. To protect the shared resources, we create a synchronization object, and use Lock(object) prior to access the shared resources. There is no nesteden-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/junfeng/archive/2007/07/30/lock-object-and-threadabortexception.aspx#4146800Tue, 31 Jul 2007 15:02:07 GMT91d46819-8472-40ad-a661-2c78acb4018c:4146800Mihailik<p>Do you have a solution for that problem yet?</p> <p>It appears to me that it must be a common major slip in 'using' and 'lock' statement implementation.</p> <p>BTW, there is a way to amortise the trouble, by wrapping Monitor's functionality in CriticalFinalizer object. Even if async exception happens, the lock will be released sometimes latter.</p> <p>But it is not the true solution in general case. I think Microsoft should address async exception problem with something substantial.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=4146800" width="1" height="1">http://blogs.msdn.com/b/junfeng/archive/2007/07/30/lock-object-and-threadabortexception.aspx#4133711Mon, 30 Jul 2007 19:16:23 GMT91d46819-8472-40ad-a661-2c78acb4018c:4133711Anderson Imes<p>I wouldn't say managed code makes it more challenging to write a reliable product - it just gives you a different set of reliability problems to worry about.</p> <p>Reliability is always a challenge, no matter what language you work with.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=4133711" width="1" height="1">