The Missing LINQ

Object relational mapping with LINQ for .NET enterprise application development

Genome O/RM uses LINQ to generate data access layers connecting relational database systems such as Microsoft SQL Server, Oracle and IBM DB2 to your .NET enterprise applications.
 
Since 20-80% of a .NET enterprise application's code deals with data access, Genome significantly reduces efforts for both development and maintenance.

Less code = less work

Code generated by Genome is lean and clean: you not only save time when building, but can also make your code more agile and easier to maintain.

Some quick facts about Genome:

• Supports the .NET Framework (versions 2.0 to 3.5)
• Fully embraces LINQ as its primary query language (Visual Studio 2008/.NET 3.5 only)
• Tightly integrates with both Visual Studio 2005 and 2008
• Supports various database platforms (MS-SQL, Oracle, IBM DB2)
• Supports both approaches: forward engineering from domain models, reverse engineering from databases 
  

• Why would I need Genome when LINQ is available now?
• Won't LINQ2SQL do the job?
• What about Entity Framework?
• So many O/RMs out there... what's Genome got to offer beyond the others?
• Isn't open source better?
• How do I convince my DBA?
• Forget the DBA - how do I convince my manager?
• Never mind all that - what would I need O/RM for in the first place?