How to use dapper instead of EF

Question

Anubhav Kumar · Answer

1. What Changes When You Move from EF to Dapper?
EF6
Dapper
DbContext
IDbConnection
LINQ queries
Raw SQL
Change tracking
Manual control
SaveChanges()
Explicit SQL (INSERT/UPDATE)
High abstraction
Low abstraction
Important:
Dapper does not replace SQL — it replaces ADO.NET boilerplate code.
2. Install Dapper
Using NuGet Package Manager:
Install-Package Dapper
Or via .NET CLI:
dotnet add package Dapper
3. Create Database Connection (Core Concept)
Dapper works on top of IDbConnection.
SQL Server Example
using System.Data;
using System.Data.SqlClient;
public class DbConnectionFactory
{
    private readonly string _connectionString;
    public DbConnectionFactory(string connectionString)
    {
        _connectionString = connectionString;
    }
    public IDbConnection CreateConnection()
    {
        return new SqlConnection(_connectionString);
    }
}
4. Simple SELECT Query (EF vs Dapper)
EF6
var users = context.Users
                   .Where(x =andgt; x.IsActive)
                   .ToList();
Dapper
using Dapper;
string sql = "SELECT * FROM Users WHERE IsActive = 1";
using (var connection = _dbFactory.CreateConnection())
{
    var users = connection.Queryandlt;Userandgt;(sql).ToList();
}
FasterFull SQL control
5. Parameterized Queries (Very Important)
Never concatenate SQL strings.
string sql = "SELECT * FROM Users WHERE UserId = @UserId";
var user = connection.QueryFirstOrDefaultandlt;Userandgt;(
    sql,
    new { UserId = 10 }
);
Prevents SQL InjectionClean and readable
6. INSERT / UPDATE / DELETE (No SaveChanges)
Insert
string sql = @"
INSERT INTO Users (Name, Email)
VALUES (@Name, @Email)";
connection.Execute(sql, new
{
    Name = "Anna",
    Email = "anna@email.com"
});
Update
string sql = @"
UPDATE Users
SET Email = @Email
WHERE UserId = @UserId";
connection.Execute(sql, new
{
    Email = "new@email.com",
    UserId = 5
});
Delete
string sql = "DELETE FROM Users WHERE UserId = @UserId";
connection.Execute(sql, new { UserId = 5 });
7. Stored Procedures with Dapper
var users = connection.Queryandlt;Userandgt;(
    "GetActiveUsers",
    commandType: CommandType.StoredProcedure
).ToList();
Passing parameters:
connection.Queryandlt;Userandgt;(
    "GetUserById",
    new { UserId = 10 },
    commandType: CommandType.StoredProcedure
);
8. Handling Transactions (Manual but Clear)
using (var connection = _dbFactory.CreateConnection())
{
    connection.Open();
    using (var transaction = connection.BeginTransaction())
    {
        try
        {
            connection.Execute(sql1, param1, transaction);
            connection.Execute(sql2, param2, transaction);
            transaction.Commit();
        }
        catch
        {
            transaction.Rollback();
            throw;
        }
    }
}
9. Repository Pattern with Dapper (Recommended)
public class UserRepository
{
    private readonly DbConnectionFactory _factory;
    public UserRepository(DbConnectionFactory factory)
    {
        _factory = factory;
    }
    public IEnumerableandlt;Userandgt; GetAll()
    {
        using var conn = _factory.CreateConnection();
        return conn.Queryandlt;Userandgt;("SELECT * FROM Users");
    }
}
CleanTestableProduction-ready
10. Replacing EF Gradually (Best Practice)
You don’t need to remove EF fully.
Hybrid Approach (Very Common)
EF → INSERT / UPDATE / DELETEDapper → SELECT / Reports / Search
Example:
// EF for write
context.Users.Add(user);
context.SaveChanges();
// Dapper for read
var users = connection.Queryandlt;Userandgt;("SELECT * FROM Users");
11. When Dapper Is a Better Choice Than EF
Use Dapper when:
Performance is criticalQueries are complexReporting / dashboardsLarge data readsStored procedures
Stick with EF when:
Heavy business logicRapid developmentComplex relationships
12. One-Line Interview Answer
“Dapper replaces Entity Framework by using raw SQL with object mapping, giving better performance and full SQL control at the cost of manual change tracking.”
and

forum

How to use dapper instead of EF

ICSM

Can you answer this question?

1 Answers

1. What Changes When You Move from EF to Dapper?

2. Install Dapper

3. Create Database Connection (Core Concept)

SQL Server Example

4. Simple SELECT Query (EF vs Dapper)

EF6

Dapper

5. Parameterized Queries (Very Important)

6. INSERT / UPDATE / DELETE (No SaveChanges)

Insert

Update

Delete

7. Stored Procedures with Dapper

8. Handling Transactions (Manual but Clear)

9. Repository Pattern with Dapper (Recommended)

10. Replacing EF Gradually (Best Practice)

Hybrid Approach (Very Common)

11. When Dapper Is a Better Choice Than EF

12. One-Line Interview Answer

Liked By

EF6	Dapper
`DbContext`	`IDbConnection`
LINQ queries	Raw SQL
Change tracking	Manual control
`SaveChanges()`	Explicit SQL (`INSERT/UPDATE`)
High abstraction	Low abstraction