Integrating with Entity Framework 4

I have been working with Microsoft's ORM technology ever since LINQ2SQL came out in 07', however before Microsoft decided to get into the ORM business, I had crafted my own ORM framework which allowed me to easily integrate data and business code within solutions I worked on. Once L2S came out I decided to integrate my ORM tool with it that way I could rely on the graphical modeling tool and transaction functionality that came out of the box. Then Microsoft decided to push Entity Framework shortly after L2S and also pointed out that EF would be in the basket with all the apples (compared to L2S). Since then some comments from the community were made about how L2S has its advantages and that it should still stay on Microsoft's radar. However, when I first started working with EF early on I thought it still had some challenges. I spoke on EF early on at a couple of user groups but for projects I was still using L2S or my custom ORM tool.

Now that I have started integrating EF 4.0 into my custom framework I have been real excited with what I have seen. I have a better looking graphical tool, easy way for updating my models and the same support for transactions. On top of that, and what I think brings it to the top is the support and customization for working with POCO (Plain Old CLR Objects) and Lazy loading, which allows you to define the relationships within code as well as the model and have them automatically loaded within the CLR objects. These features are the basis for what it takes to integrate existing ORM technologies with EF therefore being able to hit the ground running with existing code.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by: BayerWhite
Posted on: 9/16/2010 at 3:21 AM
Actions: E-mail | Kick it! | DZone it! | del.icio.us
Post Information: Permalink | Comments (0) | Post RSSRSS comment feed
Comments are closed