Entity Framework Dynamic Data Model Builder

  •        134

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).

http://dynamixdata.codeplex.com/

Tags
Implementation
License
Platform

   




Related Projects

OData over SQL Azure Federations


This is a sample project that demonstrates how to expose an SQL Azure federated database throught the WCF DataService. Entity Freamework is used as a data access layer. Both EF code first (POCO) and database first approaches are represented.

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.

EF Generic Repository Pattern


Entity Framework 4 POCO, Repository and Specification Pattern. This project makes it easier for database interaction with any kind of .Net projects. You'll no longer have to write your own DAL to access EF Entities. It's developed in C#.

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.

NQueries


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



EntityFramework6 - This is the codebase for Entity Framework 6 (previously maintained at https://entityframework


Entity Framework (EF) is an object-relational mapper that enables .NET developers to work with relational data using domain-specific objects. It eliminates the need for most of the data-access code that developers usually need to write.Entity Framework is actively developed by the Entity Framework team in collaboration with a community of open source developers. Together we are dedicated to creating the best possible data access experience for .NET developers.

Loef


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

Kerosene ORM


Kerosene is a self-adaptive and configuration-less ORM library, with a SQL syntax based on C# dynamics, WCF, and Entity Framework capabilities for POCO objects.

EntityFrameworkCore - Entity Framework Core is a lightweight and extensible version of the popular Entity Framework data access technology


Documentation on using EF Core is available at https://docs.microsoft.com/en-us/ef/core/.This project is for Entity Framework Core. Entity Framework 6 is still under active development at https://github.com/aspnet/EntityFramework6.

UnifiedASP SQL Data Access Layer


Your entity classes/data access layer should be the easiest part of your application, not some bloated mess of academic wankery. The UnifiedASP DAL gives you an easy way to structure your entity/data objects and execute SQL stored procedures.

System.Data.Entity.Repository


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

ORMAC


ORMAC is a micro ORM written for .NET. It allows custom SQL script to object mapping and easy stored procedure calls with minimum mapping and data access code.

Entity Framework Code-First Automatic Database Migration


The Entity Framework Code-First Automatic Database Migration tool was designed to help developers easily update their database schema while preserving their data when they change their POCO objects. This is not meant to take the place of Code-First Migrations. This project is ...

UnitOfWork Framework for EF CodeFirst


Simple framework for organizing Persistance Layer in DDD applications, containing base interfaces (IUnitOfWork, IUnitOfWorkFactory, necessary locators) and Layer Supertypes for Entity Framework Code First implementation of Persistance Layer (RepositoryBase etc).

Entity Framework / Linq to Sql Poco Code Generator


Code generator that produces Poco Dtos and Xml mapping code that works with both Entity Framework and Linq to Sql. You can create one set of classes that can be used with both technologies. Choose a template and hit the button. Utilizes Managed Extensibility Framework (MEF) .

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.

Snowflake


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.

Data Broker


Data Broker is a Data Access Layer and ORM framework. It is small, easy to use and implements various fault tolerant features. It requires no XML configuration for defining the object relational mapping, just some simple attributes in the data access classes. Developed in C#.

Agile ADO.Net Persistence Layer (AAPL)


I've been impressed by the coding efficiencies that can be gained from ORMs like EF or Hibernate. Those tools allow you to embrace change and work in a much more agile way. This is my attempt to produce similar results using good old ADO.Net (which is still my favorite).