Microsoft Ships Entity Framework Core 3.1 and Entity Framework 6.4 -- Visual Studio Magazine

Microsoft Ships Entity Framework Core 3.1 and Entity Framework 6.4

By David Ramel
12/04/2019

Along with new releases of Visual Studio 2019 16.4 and .NET Core 3.1, Microsoft this week shipped Entity Framework Core 3.1 and Entity Framework 6.4 for data and object-relational mapping (ORM) developers.

As with .NET Core 3.1, these are relatively uneventful shipments -- most notable for long term support (LTS) licensing -- without a bunch of fancy new features or functionality included, as the dev teams focused on firming up existing code.

"The primary goal of EF Core 3.1 is to polish the features and scenarios we delivered in EF Core 3.0," Microsoft said. "EF Core 3.1 will be a long term support (LTS) release, supported for at least 3 years. To this end we have fixed over 150 issues for the 3.1 release, but there are no major new features to announce.

"EF Core 3.1 reintroduces support for .NET Standard 2.0, rather than requiring .NET Standard 2.1 as was the case for EF Core 3.0. This means EF Core 3.1 will run on .NET Framework versions that support the standard."

EF 6.4, a holdover from the proprietary, Windows-only .NET Framework days, also focused on polishing previously introduced features and fixing issues.

About the Author

David Ramel is an editor and writer for Converge360.

Printable Format

comments powered by Disqus

Featured

Oh Data! Microsoft Ships First Major OData Update in Nearly 8 Years

Microsoft today shipped a preview of OData .NET 8. OData v7.0 was released in August of 2016.
Full Stack Hands-On Development with .NET

In the fast-paced realm of modern software development, proficiency across a full stack of technologies is not just beneficial, it's essential. Microsoft has an entire stack of open source development components in its .NET platform (formerly known as .NET Core) that can be used to build an end-to-end set of applications.
.NET-Centric Uno Platform Debuts 'Single Project' for 9 Targets

"We've reduced the complexity of project files and eliminated the need for explicit NuGet package references, separate project libraries, or 'shared' projects."
Creating Reactive Applications in .NET

In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.
AI for GitHub Collaboration? Maybe Not So Much

No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.