From the Editors: Microsoft’s changing .NET standards

March 1, 2010 —  (Page 1 of 2)
Microsoft should be more conservative about changing fundamental technologies in .NET, especially when its changes require substantial developer rework and reverse previously stated directions.

The company’s recent decision to shift from LINQ to SQL on the ADO.NET Entity Framework was unsettling to some developers, and it contributed to the confusion regarding .NET libraries and consistency. Uncertainty is anathema to developers who might be considering .NET and who don’t want to be programming for a moving target.

Developers do not welcome breaking changes and do not want to be stuck using technologies that are initially encouraged by Microsoft, but then suddenly are rendered obsolete. The fact that Microsoft has committed to a 10-year support cycle for LINQ to SQL does not inspire confidence in the enterprise, where it is not uncommon for many applications to be decades old.

Since the .NET Framework's introduction less than a decade ago, Microsoft has rapidly evolved it into a popular and productive platform for developers. The company deserves credit for its stewardship of the platform, but it needs to put the brakes on introducing new features that fragment the platform's existing technologies.

We hear accounts from developers and partners alike that struggle to keep up with the pace of change to those technologies. Continuing down that path is the wrong thing to do for customers and for .NET.

While it is true that the core of .NET has changed very little from .NET 2.0, few developers work with the base class libraries alone. The foundations that were added with .NET 3.0, along with features such as LINQ, are at the heart of many enterprise applications.

By its own admission, Microsoft would have saved itself a year of effort had it realized that developers wanted synergies between its various technologies. It took a year to right that wrong in .NET 3.5.

Businesses are betting that .NET will be a viable long-term platform, and Microsoft's partners have built businesses around it. While .NET is good, Microsoft’s inconsistency about APIs and supported technologies is not.

Related Search Term(s): Microsoft, .NET

Pages 1 2 

Share this link:


03/03/2010 05:59:21 PM EST

Yes, its about time they should slow their pace. I am a .NET developer and really find it tough to cope up with the newest and latest framework releases while I'm still settling in with the previous one. Microsoft should provide enough time to the developers to get themselves drenched in the technology, otherwise it can get really frustating.

United StatesSam Young

05/14/2010 06:58:00 AM EST

I think it's hard to lock down a future path looking forward 10+ years. I think the .NET team is striking a good balance between supporting the latest technologies and providing a stable platform. If .NET does not reflect the evolution of the development world, it will soon turn into the new COBOL. .NET is now 10 years old - that is a few lifetimes in the technology world.

South AfricaHendrik

Microsoft starts up .NET Foundation
New group should shepherd Microsoft and .NET-flavored open source into the community Read More...

News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>



Download Current Issue

Need Back Issues?

Want to subscribe?