Register       Login  
   Small text Medium text Large text
  Useful links  
Genome 4.2 SP8 supports VS2013 and .NET 4.5 - Thursday, October 24, 2013
Genome v4.2.9 provides integration to Microsoft Visual Studio 2013 with the same functionality as for VS2010 and VS2012. Also with this update the DataDomain schema projects can be compiled to .NET 4.5 and .NET 4.5.1 too. The service pack contains a few minor fixes in the runtime too.  
Genome 4.2 SP7 released - Wednesday, May 01, 2013
With a few fixes and a small feature!  
Genome 4.2 SP6 supports VS2012 RTM - Friday, August 24, 2012
Genome v4.2.7 provides integration to Microsoft Visual Studio 2012 RTM with the same functionality as for VS2010. This release contains only this tool enhancement and no change in the runtime.  
Genome 4.2 SP5 with VS2012 RC support - Friday, June 29, 2012
Genome v4.2.6 provides integration to Microsoft Visual Studio 2012 RC with the same functionality as for VS2010. This release contains only this tool enhancement and no change in the runtime.

Important note: Visual Studio 2012 RC comes with a change in the MsBuild system, that causes the Genome builds fail (in VS2012 and also in VS2010) with the following error:
error MSB4185: The function "CurrentUICulture" on type "System.Globalization.CultureInfo" has not been enabled for execution.

This problem will be fixed my Microsoft in VS2012 RTM. In the meanwhile you have to set the environment variable “MSBUILDENABLEALLPROPERTYFUNCTIONS” to “1”. (You might need to restart Visual Studio).

Genome 4.2 SP2 (v4.2.3) released - Oct 29, 2010
With many fixes and small features!  
Genome 4.2 released - Feb 10, 2010
Supports now Visual Studio 2010!  
Updated roadmap - Dec 22, 2009
learn more about the upcoming Genome v4.2 release  
Genome 4.1 released - Mar 31, 2009
Read more about what's new in this release.  
New Product Video released - Jan 16, 2009
Get a quick overview of Genome v4.  
  Genome and Entity Framework  
Many developers ask us about Microsoft's Entity Framework, which was released in August 2008 with SP1 of .NET Framework 3.5. Before comparing them though, it is important to first distinguish between LINQ to Entities and the Entity Framework.

While LINQ only plays a role in a small part of an O/RM (the query language aspect), Entity Framework is much more than an O/RM: it is Microsoft's next generation API for abstracting database access on the .NET platform.

The old ADO.NET abstracted communication between different database platforms and left it at that; it did not unify the languages or results in terms of SQL dialects, database structure and field types.

Entity Framework however does just that: it also abstracts this level of communication with databases with eSQL, which each database vendor can translate to from their own SQL dialect. The Entity Data Model (EDM) can be mapped to abstract, vendor-specific database models, yielding unified data models that can be queried with a unified query language (eSQL). However, EDM and eSQL are both still on the relational level.

O/RMs plug in on top of that. In addition to LINQ to SQL, Microsoft introduced another O/RM called LINQ to Entities with Entity Framework that maps CLR business entities to EDM entities and also translates LINQ queries in the CLR business model to eSQL. In other words, LINQ to Enitites provides an additional abstraction on top of the Entity Data Model.

How does Genome compare to LINQ to Entities?

We are currently working on a more thorough analysis of the significant differences between Entity Framework and Genome. In the meantime, please check out the technical review of Entity Framework from the lead architect of Genome.
There is also an article on the Genome team blog that gives a general view on Entity Framework and what value proposition Genome offers over it.