First, Microsoft is causing legal troubles for Jamie Cansdale of the TestDriven.Net. Yes, Microsoft is causing troubles for the TestDriven.Net guy.

"When TestDriven.Net 1.0 was released I was still hobbyist .NET developer. It was only natural that I use the Visual Studio Express editions which were being targeted at other hobbyist developers. In fact I developed the whole of TestDriven.NET 1.0 using C# Express, MSBuild and WiX (as described in this post).

A few months after TestDriven.Net 1.0 was released Microsoft made me an MVP. According to Ben Miller (my then MVP lead) I was "very well known" for having created TestDriven.Net. As far as I'm aware this was the primary reason I received the award.

On Dec 1, 2005 I received an email from Jason Weber the lead for the Visual Studio IDE and Visual Studio SDK. Apparently Jason wanted to better understand my product and strategy. It was clear from the email subject that Jason incorrectly assumed TestDriven.Net was a VSIP Package. The interesting thing about VSIP packages being that they require a special key from Microsoft in order to function."


Second, Sam Gentile, wrote that "

Many of us who are "senior" in the Microsoft community and who have done
things before, privately say we "would rather do Ruby anyway." For
instance, myself and my Principal Engineer Steve Eichert would chose
Ruby on Rails any day over the leaky abstractions that is
ASP.NET/Web Forms. There is no inherent way to have testability. But we
don't do Web Programming-). In the Smart Client world, we look outside
Microsoft for much of what we do. I agree that that people will, and
already have moved away from the Microsoft server platform because of
the Ruby situation.

On the alpha geek side, I fear all is lost already. All of my peers on
CodeBetter.com and the "Agile .NET" community have already moved onto
Castle/Windsor, NUNit, NAnt, MonoRail, Spring.NET, NHibernate, etc
instead of Microsoft solutions. Its virtually over already. For two
years now, I have talked about our Agile team and how we can't use
Visual Studio Team System and instead have to use CruiseControl.NET,
NUnit, NAnt, etc to work in an Agile fashion. Not only does Microsoft
not understand this, but the majority of Microsoft programmers don't.
They have been weaned on being "Morts" and having wizards, stored
procedures, drag & drop forced on them and not required to learn the
solid skills that make up what we think of as a developer. I am one of
those myself that is very close to moving out."