Huh? Digg effect in .NETkicks?! Mirror anyone?

You forgot that you can skip the brackets if your block consists of a single line.

OMG!

You've got to the kidding...
In another post, someone writes on the merits of being able to compare against null.

That I call detailed!

Although I find that usage awkward. Such an extension method always made more sense to me to be attached to the string, not the enum, replacing it by ref...

"Value".ToEnum<SomeEnum>();

Oh, we still do smilies in code? *sigh*

I think I'd prefer this, it's far more reusable:

public static A GetAttribute<A>(this Enum @enum)
where A : Attribute
{
if (!@enum.GetType().IsEnum)
return null;
object[] attributes = @enum.GetType().GetField(@enum.ToString()).GetCustomAttributes(typeof(A), false);
return attributes.Length > 0 ? (A)attributes[0] : null;
}

Breaking news? You mean more like breaking waves...the principal wave already arrived two frontpage posts down. ts...

That's too complicated to be on .Netkicks front page =)

Note to self: compiler-directive + using alias = use either MSTest or NUnit. Nice!

Valid post! And more on that here: http://www.lostechies.com/blogs/jimmy_bogard/archive/2008/05/19/more-entity-framework-thoughts.aspx

Ah, so I 'm actually doing monostate?
Seriously, I always thought Singleton is keeping an single instance of some object. As long as you implement all relevant ops as instance members of said object and give some entry point into your singleton keeper you're still well on your way for testability and all OO glory.

Has been around for quite a while now. I quite like it, but it should be an opt in thing:
http://research.microsoft.com/specsharp/?0sr=a - Spec# home
http://research.microsoft.com/specsharp/papers/krml136.pdf - Intro to Spec# features

Lovely...in theory developerexchange.com is still free. Go grab it! A new source of revenue for high-class dev teams?

So you recreated attached properties? Fascinating...

He is some sort of modern hero, I'd think...