Legerity
I've recently been able to upgrade to Visual Studio 2005 at work, and it is a big upgrade. The refactoring support is nothing special by the standards of other products and environments out there, but it's huge that it's shipping out of the box, and what's there is good enough to cover the really common cases, but leaves plenty of room for third party improvement. I expect that it will turn a lot of developers on to the concept.
I've been redoing a lot of the unit tests I use at work, and for this go-round, I decided to try the unit test framework that ships with VS 2005. Out of the box, there are some nice features, like the ability to generate tests for existing code. Yes, I know that's not TDD. It is nice to have an easy way to begin absolving oneself of one's past sins. The generated tests include some nice features for doing white-box testing as well. I was pretty distressed by the clumsy interface - I immediately missed TestDriven.NET's "run test on the current method" feature - I love doing development in this focused way. You can set up test configurations in VS 2005, but it's very clumsy to do so. So I was very pleased to see that recent versions of TestDriven.NET support the MS Team System test framework. Jamie Cansdale should receive some sort of sainthood for TD.NET, I just can't understand how a .NET developer could live without it.
I also saw that Peter pointed to Michael Puleio's blog. Michael worked at Galileo for a few months not long after I started there. Michael worked with me on Focalpoint, when I was nominally the team lead (of a team of two). Hopefully he's forgiven me for making him do InstallShield those many years ago. I like the Roles on an Agile Team post, especially the part about agreeing to disagree. I think that's just good advice for any situation.