ah excellent, thanks!

I'd love to, but all I get is "The XML page cannot be displayed" when I go to the article.

of of my "favorite" projects I worked on was when a developer would always do try { ScaryThing(); } catch { /* completely empty */ }, this was his exception handler for all situations.

I knew I hit one of his bugs when all of a sudden the app just stopped dead in its tracks, and boy were they fun to track down...

I agree with yesthatmcqurk. I like how dnk is rather anonymous. There's little ego inflating or reputation building going on, just good article submissions.

That's not a good example.

A property should be used for the accessor, not a method. That's what properties are for.

As it stands, it does need locks to avoid race conditions should multiple threads be accessing the same singleton at once. That implementation can lead to multiple instances of the singleton being created.

Why is this pointless blog entry getting kicked when

http://confluence.public.thoughtworks.org/display/CCNET/CCNet+1.3+Release+Notes

is the real deal?