The previous incarnation of that Microsoft article was heavily panned by critics and in a rare move, Microsoft actually pulled it out of its developer web site. I didn't realise it but Microsoft actually replaced it with one written by Jeffrey Palermo -- http://msdn2.microsoft.com/en-us/library/aa730844.aspx -- back in 2006. Most of you probably weren't aware of that either.

If you read the (updated) article though, try your very best to read how the TDD steps are actually done in VSTS. I couldn't find any!  I don't know about you but this to me is a very big indication that VSTS (at least the 2005 edition) was not actually designed to work with TDD. The tool is supposed to make it easier to create tests after you've created the code, not the other way around (which is "proper" TDD). Microsoft might as well just say that bluntly and be done with it.

I don't know how things have changed in VSTS 2008. As if I can afford it anyway. I guess the best .NET TDD tool for me (at present) is still the TestDriven.NET add-in to Visual Studio. I am also hoping that SharpDevelop can get its act together this coming year.

Have a Merry Christmas everyone!