Brian Muth wrote:
Awesome. Thanks, Alberto. I couldn't see the needle for all the hay!
Do realize that the readerwriterlock is flawed in .NET 2.0. A new one,
also with flaws but less, will be released in v3.5
Please do a google search on readerwriterlock and you'll see the
problems. There are work arounds though, though these depend on your
situation: sometimes a spinlock is enough, other times you need a
simple monitor enter/exit.
FB
--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website:
http://www.llblgen.com
My .NET blog:
http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------