Kellerman .NET Data Access Layer

Knight Data Access Layer is the swiss army knife of Object Relational Mapping, Data Access, and LINQ. A key differentiator is the ability to automatically map from classes to tables without any mapping files, attributes, visual models, or convention definitions. The auto mapper can also map SQL and stored procedure results to classes without any mapping definition. When properties and database columns are named differently; mapping can be defined using attributes, code, or XML Mapping files. Auto increment primary keys, GUID primary keys, and composite keys are supported. Mappings can even be overridden at run time.

Knight Data Access Layer is compatible with SQL Server, Oracle, MySQL Firebird, SQLite, VistaDB, Microsoft Access, PostgreSQL, or any ODBC or OLEDB compliant database. Custom database providers can be easily implemented.

There is no need to revert to ADO.NET as everything can be executed within the library. Typical operations are supported such as creating databases, creating tables, executing stored procedures, truncating tables, and executing straight SQL.

LINQ is fully supported for any select operations including: aggregate, union, skip, take and much more. Knight Data Access Layer supports LINQ to SQL Server, LINQ to Oracle, LINQ to MySql, LINQ to Sqlite, LINQ to VistaDb, LINQ to Firebird, LINQ to PostgreSQL, and LINQ to Microsoft Access.

Code First Approach, Database First Approach, and No Approach (DataTables and Dictionaries) are all supported. Several generation features are included such as creating classes from tables, creating tables from classes, synchronizing namespaces to a database, generating table scripts, and generating upgrade scripts.

Knight Data Access Layer is SDLC Environmental friendly. Mappings for Schema/Owner plus table names can be switched on the fly at run time. This is useful for switching to a different test environment, switching to use staging tables, or switching to use archive versions of tables.

Common patterns are built in such as Unit of Work Pattern, Active Record Pattern, Repository Pattern, and Session Factory

It supports all .NET project types including ASP.NET MVC, WPF, Webforms, Winforms, WCF, Windows Services, and Web Services. It can be used with any .NET language including VB.NET and C#. Download the full list of features.

Q: How do I use my license key? //Get the current thread static safe instance of the helper IDataHelper db = DataHelper.SessionFactory();

//Specify User Name and License Key from the receipt db.UserName = “John Smith 1234”; db.LicenseKey = “asdfl219==”;

Access, tables, Layer, classes, mapping, supported, database, Knight, without, primary, files, creating, attributes, Mapping, including, Approach, stored, Mappings, Pattern, switching, Access, tables, Layer, classes, mapping, database, supported, Knight, without, primary, files, creating, attributes, Mapping, Mappings, Approach, stored, including, switching, Pattern