Found 596 packages
The UnitOfWork package provides a lightweight starter kit for using the UOW, and Repository patterns with Entity Framework. It has been implemented in an easily testable way, so that you can mock data access to make testing easier.
A plugin for Microsoft.EntityFrameworkCore to support repository, unit of work patterns, and multiple database with distributed transaction supported.
Provides a unit-of-work plugin for Rebus
Provides the UnitOfWork pattern for Microsoft.EntityFrameworkCore.
Provides UnitOfWork abstractions in order to implement UnitOfWork pattern for Microsoft.EntityFrameworkCore.
Provides the UnitOfWork pattern for MongoDB.Driver.
This official URF framework minimizes the surface area of your ORM technlogy from disseminating in your application. Framework provides an elegant way to implement a reusable and extensible Unit of Work and Repository pattern.
Provides UnitOfWork abstractions in order to implement UnitOfWork pattern for MongoDB.Driver.
NetStandard2.0 and NetCoreApp2.2 Utilities for Crud API System - Unit Of Work Interface: should be referenced only by API project for Commit and Rollback actions.
A library that helps you implement a UnitOfWork pattern
Unit of work framework
Essa biblioteca tem objetivo de implementar UnitOfWork para qualquer banco de dados, implementando metodos de uso basico e comumente utilizado em projetos. Deve ser instalada no projeto Infra.IoC
Essa biblioteca possui as abstrações, ou, as interfaces que podem ser utilizadas em qualquer projeto. Porém a biblioteca contendo as implementações, deve ser instalada no seu projeto de Infra.Data
Unit of Work implementation for EntityFramework Core. For more information please see Calabonga.UnitOfWork package.
Idea.UnitOfWork Class Library
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+.
Unit of work integration for SFA.DAS
Unit of Work for Corprio API to access database