Gasp! MS interested in Whidbey compatibility??
Perhaps it was a slow news week last week. That's the only reason I could figure why a few publications found it newsworthy that Microsoft is sincerely interested in backward compatibility of .NET applications with the Whidbey runtime. There's no sense in denying it, so I admit it! It's true, all of it! Yes, beta testing has revealed some breaking changes. Yes, we have tried to connect with ISVs to perform compatibility testing with their applications. Yes, we want to fix any compatibility bugs. Heck, we're even testing some of the more popular applications in house in order to ensure backward compatibility. To me, this is just business-as-usual quality assurance for any organization writing software libraries upon which many other vendors have dependencies. But I guess if Microsoft does it, it's newsworthy.
I manage a program in the VC++ group called "T100," where we try to keep a close relationship with the Top 100 worldwide VC++ ISVs by paring each ISV with a member of our product development team. Just the day before this story came out, I sent an email to those in the group that maintain a T100 ISV relationship, asking that they get in touch with their ISV and walk them through a testing protocol for Whidbey compatibility. This is effectively the VC++ piece of a larger effort within the company to ensure broad backward compatibility with existing applications running on the upcoming Whidbey runtime. It was amusing to see this effort become news but then again, I'm still new here, so maybe I'm just not accustomed to folks publishing articles about things that would be considered normal software development practices anywhere else.
Comments
- Anonymous
April 29, 2008
PingBack from http://ezinefrontpageblog.info/texblog-gasp-ms-interested-in-whidbey-compatibility/