So, eWeek decides to post a headline article today entitled, "Microsoft .Net Framework 2.0 Breaks Apps."  Hmm.  The article itself isn't that bad, carefully note that between the blazing headline and the closing quote from "one developer familiar with breaking changes related to the rollout of Windows XP SP2, who asked not to be identified", there are lots of good points about the successes our customers have had and how we're being as thorough and careful as possible to keep developers informed and aware. Yes, there have been a few unavoidable compatibility issues, but that headline seems woefully wrong based upon my own experience with 2.0 adopters.  We've had millions upon millions of lines of code migrated already by our early adopters, and we've responded as quickly as possible to issues that come up.  We've also thoroughly documented places where impacts can happen.

In the past, we (Microsoft) might have groused about such a poorly-titled headline and moved on, but blogging allows anybody inside Microsoft to have a voice.  In this particular case, S. Somasegar, the VP of the Developer Division here, decided to respond to the article.