![]() Some of the inefficiencies he discovered hailed back to the early days of Entity Framework. Shay Rojansky, who has become “the performance guy” on the EF team, has explored the many nooks and crannies within SQL sent to the database and other related areas, discovering many points at which efficiencies could be applied. And true to their word, there was a lot of work done on updates that EF Core sends to the database. At that time, the team committed to focusing on improving the performance of other workflows in EF Core 7. Faster and Faster!īack in 2021, one of the biggest stories for EF Core 6 was the dramatic performance improvement for non-tracking queries. So, I may wait until EF Core 8 to use the new nickname. I still remember that first version of EF Core, just after EF6, which had a working name of EF7 until it became EF Core. You'll find this article filled with some of the features that will be most impactful to the bulk of dev teams as well as a few that I personally found interesting.Īlthough I will always refer to this version as EF Core 7, keep in mind that much of the documentation and other resources will use EF7 as its nickname. Not only does it mean writing about them, but I also get to test them all out, which is quite a lot of fun, thanks to the fact that I don't have to do so with the goal of releasing production code. I've been overwhelmed in trying to choose which of its features to share with you here. So you can continue using it on a supported version of. ![]() NET 6, which is the long-term support version of. Although EF Core 7 is being released alongside. That has a lot do with the fact that the team has made a big investment in creating a stable base to build on. Lately, it seems that each iteration of EF Core brings fabulous new features and improvements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |