Register       Login  
   Small text Medium text Large text
  Useful links  
   
         
     
  Announcements  
 
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!   read more...
Genome 4.2 released - Feb 10, 2010
Supports now Visual Studio 2010!   read more...
Updated roadmap - Dec 22, 2009
learn more about the upcoming Genome v4.2 release   read more...
Genome 4.1 released - Mar 31, 2009
Read more about what's new in this release.   read more...
New Product Video released - Jan 16, 2009
Get a quick overview of Genome v4.   read more...
 
         
     
  Genome and LINQ2SQL  
 
Won't LINQ2SQL do the job?

LINQ2SQL is Microsoft’s basic tool for O/RM. Like all O/RMs, it translates LINQ queries into SQL. However, it has a few limitations which can immediately disqualify if from enterprise application development. There are a few common scenarios which require enterprise-level features such as Genome’s:

  • SQL Server is not the only database platform out there, but it is the only database platform supported by LINQ2SQL. Genome on the other hand supports Oracle and IBM DB2 as well as SQL Server. Genome is also very flexible, so additional database platforms can be added, given sufficient demand.

  • LINQ2SQL only allows you to reverse engineer from existing databases, which means that you cannot model your domain and then generate the database. Instead, you can only start with the database model. Genome on the other hand lets you work in either direction: reverse engineer from an existing database or start by modeling your domain. Even when you start off with an existing database, you usually continue modeling in the domain model as well. The domain model is far more expressive than the database model, so we feel that a good O/RM tool should support either approach.

  • Brown field development is by far a more common scenario than the luxury of a green field; projects typically start off by connecting to existing databases, sometimes veritable decades-old dinosaurs with truly exotic schema patterns. This is where a flexible O/RM tool really proves its value. Genome can support the strangest schemas, and customers have even successfully mapped schemas generated with 4GL tools. This flexibility also gives DBAs the power of optimising database schemas throughout the application development cycle and beyond. Far from rendering DBAs obsolete, good O/RMs will give them better tuning possibilities for their expertise in optimising queries and database schemas (please also see our FAQ on convincing DBAs of the benefits of O/RM).
  • We are amused (but only slightly) that LINQ2SQL, while restricted to the database-first approach, nevertheless does not offer the flexibility required for working with "real", existing databases.