A package that mimics EF core actions with dapper. Used for the programmers that are not allowed to use EF core at their company
$ dotnet add package CustomDapperEntityActionsA .NET package that provides Entity Framework Core-like actions using Dapper, designed for developers whose companies restrict the use of EF Core.
CustomDapperEntityActions bridges the gap between Dapper's lightweight performance and Entity Framework Core's convenient entity management features. It offers familiar entity action patterns while maintaining Dapper's speed and flexibility.
Install via NuGet Package Manager:
[Table("[schema].[table]")]
public class Plant
{
[Key]
[Column("id")]
public int Id { get; set; }
[Column("description")]
public string? Description { get; set; }
[Column("is_active")]
public bool IsAcive { get; set; }
}
public class ApplicationDbContext : IDisposable
{
// if using postgres, sql also possible
private readonly NpgsqlConnection _connection;
private IDbTransaction _transaction;
// The entity we just made
public DapperSet<Plant> Plants { get; }
public ApplicationDbContext(string connectionString)
{
_connection = new NpgsqlConnection(connectionString);
_connection.Open();
_transaction = _connection.BeginTransaction();
// assign them
Plants = new DapperSet<Plant>(_connection, _transaction);
}
public void Commit() => _transaction?.Commit();
public void Rollback() => _transaction?.Rollback();
public void Dispose()
{
_transaction?.Dispose();
_connection?.Dispose();
}
}
bld.Services.AddScoped<ApplicationDbContext>(provider => new ApplicationDbContext(connectionString));
```C#
var insert = await dbContext.Tests.InsertAsync<string>(new Plant
{
Description = "Test",
IsAcive = true
});
var update = await dbContext.Tests.UpdateAsync(new TestLalala
{
Id = 5,
Description = "Luksass",
IsAcive = true
});
var plants = await dbContext.Tests.GetByIdAsync(5);
await dbContext.Tests.DeleteAsync(5);
4. usage