Why ORM.NET?

Mapping relational databases within object based applications is too difficult using ADO.NET

The .NET Framework data access services – ADO.NET – have introduced many improvements over previous data access technologies.

Some of these improvements include:

·        Consistent access to data sources such as SQL Server, XML, and OLE-DB.

·        A set of discrete components which separate data access from data manipulation.

·  Full support for disconnected recordsets to support n-tier applications.

·        Native support for XML 

However, despite these  improvements, developers are still unable to realize the full benefits of designing and working with an object oriented based design which references data stored in a relational database.

Some of these problems are:

• Developers must create several stored procedures or embed Transact SQL statements directly in their application to access and modify data. This presents another layer of complexity and ultimately forces a compromise to the overall application design.

• SQL Statements and stored procedures do not promote re-use

• Making changes to the underlying database create errors which are hard to detect and fix until run-time.

• Crucial business rules are dispersed between the application and data layers as well as stored procedures. Making it more difficult to enforce consistency on how data is modified and business rules applied.

Introducing ORM.NET - A Powerful Data Access Layer for .NET Developers

ORM.NET solves this problem by generating a robust and flexible set of class templates which model a normalized relational data base. The class files are generated as a fully functional .NET assembly (.DLL) which acts as a complete data access layer and extends the functionality of ADO.NET. Some of the many benefits this approach provides include:

• ALL SQL code is automatically implemented making retrievals, updates, and modifying  even complex relational joins extremely easy.

•  You write no data access plumbing code which means less time spent testing and fixing error-prone data access logic.

• Enforces consistent application design using common, object-oriented based best practices

• The resulting data layer is very intuitive to use with every method and property accessible using Microsoft’s IntelliSense feature included in Visual Studio.NET

•  Model your application using a flexible object oriented methodology while keeping your data in a normalized relational data store. ORM.NET allows developers to take full advantage of the .NET framework!

The result is an almost 40% reduction in the time it takes to build data intensive applications.

• Learn about the Benefits and Features of ORM.NET

• Learn how to use ORM.NET in minutes