Developing your Data Access Layer with ADO.NET Entity Framework 4

Entity Framework has evolved in the light of feedback. ADO.NET Entity Framework 4 is now better able to accommodate different development methodologies. A welcome improvement is the way that, the application designer now has a range of options in the way that Entity Framework creates the Data Access layer. Prasanna returns to Simple-Talk to explain the significance of the changes.

Tags: , ,


  • Rate
    [Total: 0    Average: 0/5]
  • Raul Duque

    Vote of No Confidence
    The version 2 of EF had Vote of no confidence … do you think the problems found in V2 are now solved?

  • Prasanna

    Re: Vote of No Confidence
    Most of the issues around the vote of no confidence was around persistence ignorance and testability. There are lot of improvements on the new EF version especially around supporting POCO, and making it easier to write object contexts that makes testing easy.
    It is very easy on the new version to write entities that are not tied to EF and are very easy to test. SO I would say yes, the concerns that were raised are addressed.

  • Anonymous

    POCO support is an Extension
    You should add that the ADO.NET C# POCO Entity Generator is an extension to VS2010 that has to be downloaded and added via Extension Manager from

  • Anonymous

    What does this have to do with skinning cats.. gross..

  • Anonymous

    Re: Cats
    No cats were harmed during the making of this article.

    Signed: Simple-Talk editorial staff

  • Prasanna

    Re: POCO support is an Extension
    Thx. I missed that. In addition to that, other code generators not part VS.NET itself can be found and added via the extension manager

  • David

    Thanks Message
    Thank you very much

  • fewlines4biju

    A very Gud Article
    A very Gud Article

  • lrobinson

    EF With IoC – Ninject
    I really enjoyed your article. I am working on a project now to try to familiarize myself with these new design patterns. However, I am finding it quite cumbersome to hand-create entities, then matching repositories, then IoC references within each repository, then DI containers for each entity. Please tell me there is a code generation tool to complement this new paradigm. Thanks in advance.