All about .NET, C#, and ASP.NET Core. News, tutorials, articles, projects, and more. 

.NET

EF !be honest

True that. If performance is an issue for specific things, you can always fall back to executing raw sql.
EF saves so much time. But one thing i must say about it is that it really needs more features. like upsert and bulk operations.

I like my ado and don’t plan on switching preferences! However I know that i’ll need to adjust to EF as it’s a business standard.

in EFCore 8 when they made certain queries that used to translate from “where in” now translate to “OpenJson” which is significantly slower. You can bail out of it, but you shouldn’t have to.
Some references:
<a href="https://github.com/dotnet/efcore/issues/32394" target="_blank" rel="noopener nofollow">https://github.com/dotnet/efcore/issues/32394</a>
<a href="https://www.virtocommerce.org/t/performance-degradation-in-ms-sql-database-queries-after-upgrading-to-ef-core-8-openjson-contains/731" target="_blank" rel="noopener nofollow">https://www.virtocommerce.org/t/performance-degradation-in-ms-sql-database-queries-after-upgrading-to-ef-core-8-openjson-contains/731</a>
<a href="https://stackoverflow.com/questions/77703991/entity-framework-core-8-where-in-vs-where-in-openjson" target="_blank" rel="noopener nofollow">https://stackoverflow.com/questions/77703991/entity-framework-core-8-where-in-vs-where-in-openjson</a>