Microsoft’s recently released Entity Framework 4 (EF4) is generating deserved buzz among the .NET community. It seems that people can’t wait to make the jump directly to EF4, even if they haven’t even touched EF1. The perception is that EF1 was not up to snuff when it came to important database-related tasks, but the reality might be a case of a classic, “I’ll wait for Microsoft to release the 2.0 version before I commit.” A little known fact is that the majority of the core use cases that programmers want to tackle on EF4 can already be done today on EF1. Here are a few examples.
All in all, the verdict: Some will choose to jump straight to EF4 runtime, and some may find their needs can be met using EF1. Is there something specific you’d like to do in EF4 that you feel you can’t accomplish in EF1? Here at Progress DataDirect, we are moving forward with our EF4 plans for Oracle, DB2 LUW, z/OS, iSeries and Sybase ASE – we’d love to get your input on what features of EF are most important to you.
In the meantime, click below to download and evaluate the only Entity Framework provider for Oracle that is 100% managed and has zero requirements for the Oracle OCI client!
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.