Entity Framework Core - Knowledge Base (KB)

EF query refactoring tips

This query takes almost ...40... seconds ...(runs 3 times at startup...)...:...return context.Audits .Include(a => a.Phases.Select(p => p.UserActionLogs)) .Include(a => a.Phases.Select(p => p.Reminders)) .Include(a => a.Phases.Sele...

What is the best way to acquire an IDbTransaction from an IDbContext?

An ...IDbContext... has a ...DatabaseFacade..., which has a ...CurrentTransaction... property. But the ...CurrentTransaction... is an ...IDbContextTransaction.... I want to pass an ...IDbTransaction... to Dapper....How do I get an ...IDbTransaction... ins...

What's the difference between Dapper and EF Core FromSql / ExecuteSQL?

What is the difference between EF Core FromSql / ExecuteSQL and Dapper? They are both using raw SQL commands. Is the only difference being, Dapper is faster and has higher performance than the latest Entity Framework Core?

Is it possible to utilize ASP.NET Boilerplate instead of Entity Framework Core with Dapper?

I'm new to ASP.NET Boilerplate and Dapper. From the tutorial I got to know that ASP.NET Boilerplate works with Entity Framework Core. Can we use another Data Access Layer instead of EF Core? Is ASP.NET Boilerplate compatible with Dapper?

The transaction between Dapper and EF Core fails with an error. Parallel transactions are not supported by SqlConnection.

I started using EF Core with Dapper and while trying to use them both inside a TransactionScope when I call context.SaveChanges() I get the error ...SqlConnection does not support parallel transactions.... The code is the following:...public class TestCon...

With concurrent processes, Dapper query times skyrocket.

I've built a .NET Core 3.1 API. The API does a lot of work, and the bulk of it is executing SQL Queries. Most of the API uses EF Core for its data access. However, for one particularly critical query, we've discovered that Dapper offered a significant per...