When I was still a consultant I was a strong advocate of using unit tests and code coverage to make sure the code, and the application afterwards, reached the appropriate quality level to be deployed. As Team System and Team Foundation Server weren't available - not even in CTP or beta - at that time, I used a number of well-known community-driven tools like NUnit, MBUnit, NCover, NAnt, NDoc, etc.
One of the great add-in's in Visual Studio at that time was NUnitaddin. Jamie Cansdale developed the TestDriven.NET addin. Today Jamie announced the availability of code coverage together with unit testing for all versions of Visual Studio 2005 Team Suite. He bundled NCoverExplorer with TestDriven.NET to view the code coverage results.
So far I haven't tried these tools out, but I assume they play well together and offer you the same kind of unit test/code coverage functionality as you can get with Visual Studio 2005 but for all versions of Visual Studio 2005. So no excuses anymore to not unit test and test the code coverage of your classes!
Soma announced on his blog today that Team Foundation Server will ship in March. Team Foundation Server is the cornerstone of the Visual Studio 2005 Team System. More info on TFS can be found on http://msdn.microsoft.com/vstudio/products/newfeatures/default.aspx. Check the impressive list of the new features!
I know a couple of ISVs who will be very happy with this news. They have been using TFS and Team System since a couple of months and are well prepared to move to the RTM version. This blog post "Preparing to upgrade to RTM", dating from the Team System launch timeframe, can be put in practice now.