Knight Data Access Layer
Why is Knight Better

On a typical project, many technologies may be used for data access.  NHibernate or Entity Framework may be used as an ORM, a third party LINQ provider may be used to retrieve records, and sometimes it is necessary to fall back to ADO.NET.  We created Knight Data Access Layer to be the Swiss Army Knife of all data access.  It combines the features of a zero configuration object relational mapper, LINQ Provider, ADO.NET wrapper, database generator, table synchronizer, class generator, and upgrade script generator. 

There are many good ORMs out there; most of which require complex configuration.  We took a different approach, to be completely automatic.  The goal is; the less code to maintain, the better. 

The other thing that most ORMs are missing is flexibility.  Knight Data Access layer can override mapping with attributes, code, or XML files. 

 

What other framework can save an object with only two lines of code without any mapping?  None.

IDataHelper db = DataHelper.SessionFactory();

db.Save(new Invoice());