I'm with Scott on this one. The fact that Microsoft duplicates the efforts of their own community is simply inexcusable. Why does this bother me? Using the best tool or library to do the job is al it takes, right? Wrong! The problem starts with companies (including the one where I work for) that use the crappy Microsoft alternatives in favor of their open-source counterparts. Why? Simply because it has a Microsoft label on it. And this kind of decision making starts to piss me off.
Take NUnit for example. I'm using it for a couple of years now without a single complaint. Recently I've got a lot of questions why I'm not using Team System Unit Test. It sucks too much right now (you can read my comparison over here). Roy Osherove mentioned on his blog this week that the upcoming Team System Unit Test capabilities may finally be "OK". It's about time, don't you think? They finally managed to get the basic features of a unit test framework implemented. Great! But it doesn't change a thing. If someone wants me to convert all my unit tests to another unit test framework then it better be worth it. And frankly, at the moment it's not, not even the with new features in Visual Studio "Orcas". Switching to something like MbUnit is much more like it.
Unit test frameworks is just one thing. So, how long before Microsoft releases a mock object framework? Place your bets ...
