Dapper.FastCrud 1.0.1

Simple extensions added to the IDbConnection for convenience and a less error prone experience. This library is 2x faster than Dapper.SimpleCRUD.
For Dapper constructs in general, it is recommended to use Visual Studio 2015 for features such as nameof and string interpolation but that's not a requirement.

The package contains .NET 4.5 and 4.6 DLLs, one of which will be installed based on the target framework in your project.
For .NET 4.5, the code contains the polyfills for the missing FormattableString class, which is required when targetting that framework version and using string interpolation with the C# 6 compiler in VS 2015.

Examples of usage:
-------------------
- dbConnection.Insert(newEntity);
- dbConnection.Get()
- dbConnection.Get(new Entity() {Id = 10});
- dbConnection.Update(updatedEntity);
- dbConnection.Delete(entity)
- dbConnection.GetTableName<Entity>()
- dbConnection.Find<Entity>(
       whereClause:$"{nameof(Entity.FirstName}=@FirstNameParam",
       orderClause:$"{nameof(Entity.LastName)} DESC",
       queryParameters: new {FirstNameParam: "John"});

This is where the power of the C# 6 compiler comes into play, and leaves no chance to mistypings or to problems arising from db entity refactorings.

Features:
----------
- Support for LocalDb and Ms Sql Server (more coming soon)
- Entities having composite primary keys are supported
- All the CRUD methods accept a transaction and a command timeout
- Fast pre-computed entity mappings
- A generic T4 template is also provided for convenience. Isolated entity generation via separate template configurations.
Existing POCO entities are also supported which can be decorated with attributes such as Table, Key and DatabaseGenerated.
Column name overrides are not supported and not recommended. As you'll end up writing more complex SQL queries, outside of the domain of this library, you'll want to use the nameof operator as much as possible.

There is a newer version of this package available.
See the version list below for details.
Install-Package Dapper.FastCrud -Version 1.0.1
dotnet add package Dapper.FastCrud --version 1.0.1
<PackageReference Include="Dapper.FastCrud" Version="1.0.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Dapper.FastCrud --version 1.0.1
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: Dapper.FastCrud, 1.0.1"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Dapper.FastCrud as a Cake Addin
#addin nuget:?package=Dapper.FastCrud&version=1.0.1

// Install Dapper.FastCrud as a Cake Tool
#tool nuget:?package=Dapper.FastCrud&version=1.0.1
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

NuGet packages (8)

Showing the top 5 NuGet packages that depend on Dapper.FastCrud:

Package Downloads
Smooth.IoC.Dapper.Repository.UnitOfWork
The package Provides a solution for the Repository and UnitOfWork patterns together with inversition of control. On the project site there are examples of Autofact, Castle.Windsor, Ninject, Simpleinjector, StructureMap, and Unity integration. The IoC framework is not an issue... It is ment to integrate nice and smooth like... The project uses tor its repository work Dapper as ORM and Dapper.FactCRUD for fluentness. But you can use is as a foundation and with any IDbConnection and IDbTransient framework you like. The library gives you the building blocks to: * Create Sessions from the IDbFactory in your methods, IDbFactory should be injected into your class's. As Session extends IDbConnection and will Open on the factory spawning the session and dispose the connection on disposal of the connection. * Your Sessions can create UnitOfWork's. As Session extends IDbConnection and will Open on the factory spawning the session and dispose the connection on disposal of the connection. * If your logic just needs "just a" UnitOfWork with a session that has the same scope, the factory can create it for you. * The IRepository and abstract concrete class should be used on your individual repository classes to provide simple and basic calls. But ofcasue you can add all the queries you want into your Repositories and use the dapper and dapper.FastCRUD (or any other extensions) functionality provided to you. * The repository abstract classes use Dapper.FastCRUD to give you a fluent ORM experience with the most common calls. * This library does not lock you to using dapper and FastCRUD, you can use any library you like that extends IDbConnection and IDbTransation, and still use the IDbFactory, ISession and IUnitOrWork. * Implemented for .net 4..0, .net 4.5.2, .net 4.6.1, .net 4.7.1+, .net 1.6 standard, .net 2.0 standard+.
Tolitech.Modules.Base.Data
Biblioteca base para a camada Data. Esta é uma biblioteca utilizada em todos os projetos Tolitech, inclusive os gerados pela ferramenta Code Generator. Mais informações em http://www.codegenerator.com.br/
Proactive.DataRepository
Proactive data repository NetStandard package.
Cql.Core.SqlServer
A common library SQL server.
DataQI.Dapper.FastCrud
Data Query Interface it's Dapper.FastCrud provider that use infraestructure provided by DataQI.Commons and it turns your Data Repositories a live interface.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version History

Version Downloads Last updated
2.5.0.39 329,072 4/19/2018
2.4.1 154,445 10/27/2016
2.4.0 6,103 9/21/2016
2.3.2 7,712 2/9/2016
2.3.0 1,388 1/2/2016
2.2.0 1,315 12/8/2015
2.1.2 1,288 10/30/2015
2.1.0 1,173 9/18/2015
2.0.0 1,318 6/1/2015
1.1.1 877 5/21/2015
1.1.0 902 5/21/2015
1.0.2 1,404 5/18/2015
1.0.1 990 5/16/2015
1.0.0 908 5/16/2015
Show less