lol @ raindogmx

RE CVertex: The .NET 3.5 ReaderWriterLockSlim is an entirely different implementation of a reader writer lock; it is by no means the same as the ReaderWriterGate discussed in the article.

Oldie, but not too many folks know about this lock or the other high-performance threading tools inside the PowerThreading lib. Definitely worth your while.

Very helpful description and example.

The whole thing was pretty bad, lol.

Reminds me of MCPlusPlus. No, not managed C++, but MC++ the rapper: http://www.mcplusplus.com/

@foobar

If your SQL is getting very complicated, it's likely your logic should be moved out of SQL and into your business layer. SQL should be for storing data, not complex business logic.

Of course, I can't give absolute advice without understanding your codebase, but in general, if you're doing crazy complex stuff in SQL, it may be the wrong place for it.

Best mock framework around, IMO. Highly recommended.

Just needs a live demo.

Great video!

.NET 3.5 now includes ReaderWriterLockSlim, which is the official replacement for the buggy, dangerous ReaderWriterLock.

Woo! Been looking forward to this. Now I can finally try out Scott Guthrie's tutorial on Silverlight 2: http://weblogs.asp.net/scottgu/archive/2008/02/22/first-look-at-silverlight-2.aspx

That's kind of blog spam. The original post is at http://www.onlamp.com/pub/a/onlamp/2007/08/09/mono-a-progress-report.html

Yep, tagged appropriately.

Tagged appropriately.

The summary alone is gushing with Google fan-boyism, it makes me near sick. We need to come up with a name for such Google gushing. I hereby dub such nonsense as a googasm.