A few year ago, we developed a large ASP.Net application (C# / .net 3.5) that had to be "Database Engine" non-dependent (meaning this application could either use SQL Server, Oracle, MySQL ... as DB engine). For that, we used Enterprise Library Data Access Block 4.1.
But now, as we are on a "performance/scalability improvement" phase, we are thinking about technology upgrade or re-design of our application foundations.
So, the question is: is there any advantage to move to Entity Framework ? Does EF will keep our non-dependent "Database Engine" criteria ? Or should we keep our EntLib DAAB implementation but upgrade to the latest version (5.0) ?
Thanks
There is a number of EF providers for Oracle (Devart dotConnect for Oracle, DataDirect) and MySQL (Devart dotConnect for MySQL, MySQL Connector /NET), and Microsoft provides an Entity Framework provider for SQL Server, so there should not be any problems with database independence.