as an almost 20 year DBA, I have to say I LOVE EF. We have a very complicated db with hundreds of tables, and not ONE single stored proc. We have a multi-tier solution, with a ef layer, a service layer, a wcf layer, a client BL, and the UI. If I need to change a column in the table, I change it in db, update ef, change my two translate methods to object, change the object to include the column, update all service refs, and I'm done. Period. Its truly awesome. The secret sauce is using translate methods as documented in Mike Liu's book, WCF 4.0 multi-tier services development with ling to entities.
as an almost 20 year DBA, I have to say I LOVE EF. We have a very complicated db with hundreds of tables, and not ONE single stored proc. We have a multi-tier solution, with a ef layer, a service layer, a wcf layer, a client BL, and the UI. If I need to change a column in the table, I change it in db, update ef, change my two translate methods to object, change the object to include the column, update all service refs, and I'm done. Period. Its truly awesome. The secret sauce is using translate methods as documented in Mike Liu's book, WCF 4.0 multi-tier services development with ling to entities.
Entity Framework?! pfftt ...pfftt