A nice set of articles regarding non-collection related Generics development.

Part 1 discusses an elegant way to perform Lazy Load to a type. ( my personal favorite )
http://honestillusion.com/blogs/blog_0/archive/2006/10/02/Generics-without-Collections.aspx

Part 2 introduces a way to filter collections.
http://honestillusion.com/blogs/blog_0/archive/2006/11/07/Generics-without-Collections-_2800_pt-2_2900_.aspx

Part 3 shows a way to parse strings into Enum values.
http://honestillusion.com/blogs/blog_0/archive/2006/11/20/Generics-without-Collections_2C00_-Pt.-3.aspx

I was trying to figure out which unit testing framework to adopt on a project I’m involved with. My hunch was definitely NUnit & MbUnit ( where appropriate ), but a couple of dudes in the project pulled an impressive comparison table that almost had me convinced on choosing Visual Studio Team Test. Then I stumbled upon the following post by Roy Osherove ( bow down ) which made me realize that Visual Studio Team Test is probably not the way to go any time soon. Make sure you read the discussion following the post.

The main issues that pissed me off are:

• Bugs - Sure, NUnit has bugs as well, but at least its open-source and frequently released.
• Coupling to Visual Studio - No standalone UI.
• Inheritance Not Supported - The showstopper. If you can’t inherit, your are prone to sloppy design which will eventually lead you to code duplication and/or poor coverage. see http://vaultofthoughts.net/TestMethodInTheAbstractClass.aspx.

http://weblogs.asp.net/rosherove/archive/2006/09/24/MbUnit-vs.-NUnit-Vs.-Team-System-Unit-Testing-_2D00_-Choosing-a-unit-test-framework.aspx

We use the Strategy pattern all the time (some knowingly and some by some sort of fluke).

Here is a nice a way to implement Strategy without the overhead of interfaces. It’s a bit anti-OO, but is useful when there is no concrete need to create a new type just to perform some logic.

http://www.lowendahl.net/showShout.aspx?id=115

Very concise article. This articles briefly explains what to look for in C# 3.0.

http://dotnetslackers.com/articles/csharp/Csharp_3_0_An_Introduction.aspx

Unless you are applying design techniques to your unit tests, they can become quite messy. In such cases, being familiar with these anti-patterns can help you stay away from trouble.

http://blog.james-carr.org/?p=44