News

Previews Released for Entity Framework Core 3.0 and Entity Framework 6.3

Microsoft has shipped the eighth previews for Entity Framework Core 3.0 and Entity Framework 6.3, with the dev team continuing its efforts to revamp problematic LINQ functionality.

Both Entity Framework 6.3 -- previously part of the old Windows-only .NET Framework -- and Entity Framework Core 3.0 are data development options for the .NET Core 3.0 milestone release coming next month that furthers Microsoft's cross-platform, open source transformation of .NET.

However, as we detailed earlier, the dev team found obstacles in moving LINQ to .NET Core.

LINQ (Language Integrated Query) uses C# code to query various types of data stores, providing IntelliSense, strong typing and other benefits in an alternative to SQL queries.

For months, the dev team has been wrestling with the new LINQ implementation in EF Core, and that work continued in the new preview 8.

"The LINQ implementation in EF Core 3.0 is designed to work very differently from the one used in previous versions of EF Core, and in some areas, it's still a work in progress," said program manager Diego Vega in an Aug. 13 announcement post. "For these reasons, you are likely to run into issues with LINQ queries, especially when upgrading existing applications." Workarounds were detailed for those issues.

While the team struggles with LINQ in EF Core 3.0, it's also focusing on update functionality.

"At this point, we are especially interested in hearing about any unexpected issues blocking you from upgrading to the new releases, but you are also welcome to try new functionality and provide general feedback," Vega said.

Thus, while few new features were announced, some 68 issues were resolved since preview 7, with more than 50 other fixes already done that didn't make it into preview 8.

On the EF 6.3 side, things are also a bit sticky, as Vega detailed a workaround for working with EDMX files until a new updated EF6 designer debuts in Visual Studio for .NET Core projects. Beyond that, upgrading from the old way (EF6) to the new way (EF Core) seems to be a major concern for the EF6 dev team.

"With the added ability to execute migration commands against .NET Core projects in Visual Studio 2019, most of the work planned for the EF 6.3 package has been completed," Vega said. "We are now focused on fixing any bugs that arise."

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube