locked
Enterprise Library VS Entity Framework which is industry standard? RRS feed

  • Question

  • User619554136 posted

    I'm new to EF and EL data block.

    both are data accessors. but which one is used by the industry currently. What is the reason If any specific?

    EL is itself comes under best practices then why EF?

    Could any one please provide me the information.

    Thanks, Dutt

    Sunday, January 30, 2011 11:44 PM

Answers

  • User-821857111 posted

    They are completely different animals. The DAAB is a data access library (wrappers around ADO.NET), whereas the Entity Framework is an Object Relatonal Mapper. They don't do the same thing. If you want to use a data access library, Microsoft would recomend the Entity Framework. If you want to use an ORM. they would recomment EF.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, January 31, 2011 1:31 AM
  • User-821857111 posted

    You would not use EF and the Enterprise library together.

    The Entity Framework creates its connections and manages that for you. Connection pooling is managed by the underlying ADO.NET data provider, which in the case of SQL Server is SqlClient. The Entity Framework will use SqlClient if you are connecting to a SQL Server database.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, January 31, 2011 5:06 AM

All replies

  • User-821857111 posted

    They are completely different animals. The DAAB is a data access library (wrappers around ADO.NET), whereas the Entity Framework is an Object Relatonal Mapper. They don't do the same thing. If you want to use a data access library, Microsoft would recomend the Entity Framework. If you want to use an ORM. they would recomment EF.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, January 31, 2011 1:31 AM
  • User619554136 posted

    Thanks Mike I'm clear now. However...

    They don't do the same thing. If you want to use a data access library, Microsoft would recomend the Entity Framework. If you want to use an ORM. they would recomment EF.

    In above sentense

    They don't do the same thing. If you want to use a data access library, Microsoft would recomend the Enterprise Library Data access block. If you want to use an ORM. they would recomment Entity Framework.

    Please correct me If I'm wrong.

     

    Monday, January 31, 2011 3:12 AM
  • User-821857111 posted

    In above sentense

    They don't do the same thing. If you want to use a data access library, Microsoft would recomend the Enterprise Library Data access block. If you want to use an ORM. they would recomment Entity Framework.

    Please correct me If I'm wrong.

    Sorry - my mistake. You are correct.


    Monday, January 31, 2011 4:25 AM
  • User619554136 posted

    Thanks Mark. Your answer helped me.

    Monday, January 31, 2011 4:36 AM
  • User619554136 posted

    Hi Mark,

    another query on same topic.

    Can we use Entity Framework on top of Enerprise Library Data block.

    I mean EF for ORM programing

    and

    EL DB Block for creating connections and for pooling logic?

    is this a practice or just my assumption?

    Monday, January 31, 2011 4:54 AM
  • User-821857111 posted

    You would not use EF and the Enterprise library together.

    The Entity Framework creates its connections and manages that for you. Connection pooling is managed by the underlying ADO.NET data provider, which in the case of SQL Server is SqlClient. The Entity Framework will use SqlClient if you are connecting to a SQL Server database.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Monday, January 31, 2011 5:06 AM
  • User619554136 posted

    Thanks Mark for the answer. It's clear now.

    Monday, January 31, 2011 5:08 AM