dotnet_logo Looks like the latest version of the Microsoft ADO.NET Entity Framework has been released out on the ADO.NET web site. 

http://msdn2.microsoft.com/en-us/data/aa937695.aspx

One interesting item of note in the press release is that a number of companies have announced support for the framework within 3 months of RTM.  These companies include:

  • Core Lab. Providing connectivity to Oracle, MySQL, PostgreSQL and SQLite databases
  • IBM. Providing connectivity to both IBM DB2 data server and Informix Dynamic Server (IDS) databases
  • MySQL AB. Providing connectivity to MySQL databases
  • Npgsql. Providing connectivity to PostgreSQL database versions 7.3+ and 8.x
  • OpenLink Software. Providing connectivity to Oracle, Informix, Ingres, Sybase, MySQL, PostgreSQL, DB2, Progress and Microsoft SQL Server databases, and any data source accessible via OpenLink ODBC or JDBC bridge drivers
  • Phoenix Software International. Providing connectivity to SQLite databases
  • Sybase. Providing connectivity to SQL Anywhere databases
  • VistaDB Software. Providing connectivity to VistaDB databases

There are 2 other companies pledging support within the 2008 timeframe:

  • DataDirect Technologies. Providing connectivity to multiple data stores including Oracle, Sybase, Microsoft SQL Server and DB2 via DataDirect Connect® for ADO.NET
  • Firebird. Providing connectivity to Firebird databases

Having Entity Framework support from so many companies so soon after RTM will really help make it easier for companies and individuals that are wanting to move to EF to make that transition.  Today, LINQ is supported through LINQ to SQL, LINQ to Objects, and LINQ to XML.  EF extends the power of LINQ to multiple databases through ADO.NET, making it easier for developers to work with data in databases other that SQL Server.  This announcement, coming on the heels of the Microsoft Sync Framework announcements, makes for a lot of reading I need to do this weekend...

There has been a lot of debate about the value of EF as compared to encumbent technologies such as NHibernate, and I'd be curious to hear your views on whether EF is something you think developers should embrace or ignore.