•        0

Entity framework code first framework wrapper with support for generic repository pattern, N-Tier application and Transaction Management for rapid development



Related Projects

Entity Framework Dynamic Data Model Builder

Dynamic Data Model Builder lets you to have a Data Access Layer at runtime. It creates dynamic DbContext, DbSet and POCO based on Entity Framework (Code First).


Transactional data access layer using UnitOfWork and Repository patterns against IQueriables. Key features: - plain pocos - multithread spanning transactions - loose coupled from the Entity Framework - easy transaction/datacontext management

EFH - Entity Framework Helper

Entity Framework Helper was created to improve the productivity when developing using Entity Framework. By using the EFH you wont need to worry about context anymore, and it is just one example. It's developed in C# using .NET 4.0.


We wrote your data layer so you don't have to. Developed at ettaingroup for our clients. We found that we were using the same patterns over and over again. So we developed this data framework. It uses Entity Framework 4.2, DbContext and POCO's. The Generic Repository l...


Loef (said "loaf") is a set of utility classes and T4 (.tt) templates to help with setting up a proper data access layer using Entity Framework v4. - Auto generation of DTO classes - Strongly typed eager fetching - Singleton instance of your ObjectContext ready for ASP.NET or WCF


Snowflake makes the life easier for each developer that is using LINQ To SQL as data access layer in his project. It's lightweight data access framework on the top of LINQ To SQL Framework. It follows the same ideas behind DataTable and DataRow in ADO.NET, but in entity context.

AuditDbContext - Entity Framework Auditing Context

AuditDbContext provides entity change auditing for Entity Framework POCO entities.


Using the repository pattern with entity framework can be difficult. Creating a code base in such a way that the developer doesn't have to remember to do basic things with a DBContext. The biggest would be properly disposing of it. The repo helps show developers how to create a reporistory pattern in MVC4 that interacts with Entity Framework 4.3.1

N-Tier Entity Framework

The N-Tier Entity Framework extends Microsoft's Entity Framework (EF) to provide support for n-tier software solutions while keeping its simplicity.

AnimalKingdom - An Entity Framework DbContext inheritance test

An Entity Framework DbContext inheritance test

NLayer - This is a N-Layer architecture example of a .NET application using Entity Framework 5.

This is a N-Layer architecture example of a .NET application using Entity Framework 5.

ASP.NET MVC DB Editor (Entity Framework, AJAX Validation, AJAX Paging)

Simple template for ASP.NET MVC (C#) database table editor with following features: 1. Entity Framework model. 2. Data Annotations validation. 3. AJAX validation with floating-point numbers validation fix. 4. Table paging with AJAX, jQuery and browser history. 5. Authenti...

Entity Framework Oracle Provider - EFOracleOdpProvider

Entity Framework Provider for Oracle databases which uses 11.1 as the data access client. Based on the MS EFSAmpleProvider project. Developed in C#

Generic Queryable Data Repository

This is a .Net generic queryable repository that can be used in a variety of projects - most easily used with Entity Framework Database First.

Entity - [READ-ONLY] Mongo ORM for PHP. (master at Webiny/Framework)

Entity component is an ODM layer for MongoDB. Entity classes created using this component will serve as the main building blocks for modules, forms, tables, etc. Every entity attribute is a complex data type. There are no simple strings or integers. Even boolean is a complex data type and has a separate class. This allows us to generate a lot of code and interface elements automatically.

ef-change-notify - A change notification framework for Entity Framework 5.

A change notification framework for Entity Framework 5.

Coconut Dal

Coconut Dal is a lightweight data access layer, for use in projects where developers might otherwise be tempted to write native ADO.NET code instead of using a fully-featured library, such as Entity Framework or Microsoft's Enterprise Library.