none
Integration and Compatibility of EF with DAAB

    Question

  • Hi.

    I had read all the documentation of the EF and I don't find anything about the integration or compatibility with the Data Access Application Block (DAAB), someone please can give some clues or examples of integration.

    If this integration doesn't exists can you give some feedback about this as :
    - Will be supported in the future releases (DAAB)?.
    - The EF will be or is fully compatible with the Enterprise Library?
    -  An additional comentary about this point?

    Regards,
    Yuri Hinojosa
    Monday, October 01, 2007 2:31 PM

Answers

  •  

    The EF has some similarities with the Enterprise Library which includes the DAAB, but is not intended to be compatible with the DAAB.  If you look at the overview of the DAAB you'll see the following text:

     

    >>>>>

    The patterns & practices Enterprise Library is a library of application blocks designed to assist developers with common enterprise development challenges. Application blocks are a type of guidance, provided as source code that can be used "as is," extended, or modified by developers to use on enterprise development projects. This release of Enterprise Library includes application blocks for Caching, Cryptography, Data Access, Exception Handling, Logging, Policy Injection, Security and Validation.

    >>>>>

     

    The key phrase here is that application blocks are a type of guidance.  They aren't intended to be a replacement for the .NET Framework.  We've used learnings from the DAAB as input into the Entity Framework, and expect that most developers using the DAAB in 3.1 or earlier versions of the Enterprise Library will want to move to the Entity Framework rather than using the DAAB.  Because the Enterprise Library is always evolving, it is possible that we'll add future releases of it that include an updated DAAB on top of the Entity Framework, but at this time we don't have plans in place to do so.  I'd be interested in knowing if there are particular aspects of the DAAB that you'd like to use that aren't addressed by the Entity Framework or if your concern is more around migration of your code from the DAAB to the EF. 

     

    -Lance 

    Sunday, October 07, 2007 4:30 PM
    Moderator

All replies

  •  

    The EF has some similarities with the Enterprise Library which includes the DAAB, but is not intended to be compatible with the DAAB.  If you look at the overview of the DAAB you'll see the following text:

     

    >>>>>

    The patterns & practices Enterprise Library is a library of application blocks designed to assist developers with common enterprise development challenges. Application blocks are a type of guidance, provided as source code that can be used "as is," extended, or modified by developers to use on enterprise development projects. This release of Enterprise Library includes application blocks for Caching, Cryptography, Data Access, Exception Handling, Logging, Policy Injection, Security and Validation.

    >>>>>

     

    The key phrase here is that application blocks are a type of guidance.  They aren't intended to be a replacement for the .NET Framework.  We've used learnings from the DAAB as input into the Entity Framework, and expect that most developers using the DAAB in 3.1 or earlier versions of the Enterprise Library will want to move to the Entity Framework rather than using the DAAB.  Because the Enterprise Library is always evolving, it is possible that we'll add future releases of it that include an updated DAAB on top of the Entity Framework, but at this time we don't have plans in place to do so.  I'd be interested in knowing if there are particular aspects of the DAAB that you'd like to use that aren't addressed by the Entity Framework or if your concern is more around migration of your code from the DAAB to the EF. 

     

    -Lance 

    Sunday, October 07, 2007 4:30 PM
    Moderator
  • Thank you very much for your response.

     

    Currently we are evaluating EF and DAAB to replace/improve our data access layer for this reasons:

     

    - Dataset objects are not friendly to be used in other layers as PL, for that we create custom entity objects (DTO’s) for all tables in the database and make wrapper method’s to convert from DTO to DataTable and vice verse (yeah it’s insane).

    - Maintain our custom objects are expensive for any change in the database.

     

    As you can see DAAB is not a good option because we will do the same work, doesn’t evidence a difference to the common DataSet concept, in the other hand EF are much more interesting because we can share the same objects along all the application, we can put another level of abstraction using complex types, and much more.

     

    We are waiting anxiously the official release of EF.

     

    Tuesday, October 09, 2007 9:36 PM