EF Core or Dapper? A deliberate split instead of one ORM everywhere
Use EF Core where you change data and Dapper where you read it for a screen or a report. Here is why the split works, with runnable code that shares one connection.
Use EF Core where you change data and Dapper where you read it for a screen or a report. Here is why the split works, with runnable code that shares one connection.