Dapper.Data
1.6.0
See the version list below for details.
dotnet add package Dapper.Data --version 1.6.0
NuGet\Install-Package Dapper.Data -Version 1.6.0
<PackageReference Include="Dapper.Data" Version="1.6.0" />
paket add Dapper.Data --version 1.6.0
#r "nuget: Dapper.Data, 1.6.0"
// Install Dapper.Data as a Cake Addin
#addin nuget:?package=Dapper.Data&version=1.6.0
// Install Dapper.Data as a Cake Tool
#tool nuget:?package=Dapper.Data&version=1.6.0
Trivial micro-orm implemented on Dapper, streamlines connection and transaction management while preserving flexibility and usability.
***************************************
// To create an instance of database context inherit DbContext
class TestDb : DbContext
{
private const string ConnectionName = "DefaultConnection";
private TestDb()
: base(ConnectionName)
{ }
}
// execute multiple statatements using same connection
// connection and transaction (if needed)
var db = new TestDb();
db.Batch(s =>
{
s.BeginTransaction();
try
{
s.Execute([Your query]);
s.CommitTransaction();
}
catch
{
s.RollbackTransaction();
throw;
}
});
// using it with ninject
kernel.Bind<IDbContext>().To<TestDb>().InSingletonScope();
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net40 is compatible. net403 was computed. net45 was computed. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
- Dapper (>= 1.8.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
* 1.6
* Refactored common common commands in to IDbCommand interface
* Added multi mapping query support
* 1.4
* DbServiceProvider now implements IServiceProvider
* For is obsolete use GetService to retreave services
* Included T4 template to use on dataset to create services. T4 name must match dataset name. Also when adding dataset clear its custom tool property. The dataset is used only as GUI designer for your POCO(s) and services. The T4 will create one interface per table and a one interface that implement's IDbService and one base class that inherit's DbService eposing all queries defined in dataset as methods.
* 1.0
* Streamlined connection and transaction management
* Batch query processing
* Can use ninject
* Thread safe
* Connection can be defined in .config file