Microsoft's changing .NET Framework standards

WEBINAR:
Live

Full Text Search: The Key to Better Natural Language Queries for NoSQL in Node.js


Date: 1/31/2018 @ 2 p.m. ET

Microsoft news: Here Microsoft goes at it again: fixing a wheel that ain't broke... Microsoft decided to shift from LINQ to SQL on the ADO.NET Entity Framework earlier this month. This decision was quite unsettling to some .NET developer, and it contributed to the confusion regarding .NET Framework libraries and consistency.

.NET 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, the .NET Framework has rapidly evolved into a popular and productive platform for .NET developers. Microsoft does indeed deserve credit for its stewardship of the .NET platform, but it needs to put the brakes on introducing new features that fragment the .NET platform's existing technologies.

.NET developers and partners alike struggle to keep up with the pace of change to these .NET technologies. Continuing down this current path that Microsoft is on, is the wrong thing to do for customers and for .NET.

The core of .NET Framework has changed very little from .NET Framework 2.0, few developers work with the base class libraries alone. The foundations that were added with .NET Framework 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 Framework 3.5.

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

Microsoft news: Microsoft decided earlier this month to shift from LINQ to SQL on the ADO.NET Entity Framework

View Article



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Using Internet of Things (IoT) technologies, colleges and universities are linking anything and everything to create new applications that elevate the campus experience. It's called a Smart Campus. And it's transforming campus life for students, faculty and visitors. When everything is connected, devices and applications can interact with users and with each other in ways that weren't possible before: digital classrooms, connected campus ID cards, connected lighting and building environmental systems and …

  • IT planners have far more options as to where to run their workloads than ever before. On-premises data centers, co-location facilities and managed services providers are now joined by hybrid multi-clouds – a combination of Software-, Infrastructure- and Platform-as-a-Service (SaaS, IaaS, and PaaS) execution venues. All have unique operational, performance and economic characteristics that need to be considered when deploying workloads. Submit the form to watch this webinar replay featuring 451 …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date