Last post Jul 30, 2010 06:06 AM by Jonelle
Jul 28, 2010 07:02 AM|aviadfe|LINK
The entlib 5 sugest me to use with data accessors for mapping data from database to my data objects (ORM).
But in .NET 3.5 and especially in .NET 4, I can use in entity framework as ORM methodology for data objects.
What data accessors uses advantages over the entity framework?
What differences that should be affect on my using decisions?
EntLib 5 Data accessors
Jul 28, 2010 09:00 AM|Jonelle|LINK
There are 2 reasons why you'll want to use an ORM
1) Unit testing your database logic
2) Decopling your database logic from your business objects.
If these 2 are so important to your project, then go with Entity Framework.
Jul 28, 2010 10:39 AM|aviadfe|LINK
Thanks for your answer.
So, what do your considerations to use EntLib 5 data accessors (read only ORM) and not Entity framework?
Jul 30, 2010 06:06 AM|Jonelle|LINK
Sorry for the delay. Not had the best week at work.
I'll consider using enterprise library if I wanted a bit more visibility/control over the database connection management and queries sent to the database. Jury's still out on how good the persistence mechanism is in Entity Framework 4.0.
Like before, if unit testing and decoupling are not such a big deal to your project and your company, then you could stick with the Enterprise Library.