Tuesday, May 12, 2009
A while back I posted that I was looking into the viability of using Entity Framework, and at the time I was genuinly excited about what it had to offer. I even stated that I would report back to you my findings. So I set out to try and create a domain layer that used EF as an O/R Mapper but also tried maintained percistance ignorance with the data objects it was passing around. Percistance Ignorance being the objects containing the data retrieved from the database should not contain any information about the mechanism it used to retrieve the data.
To be honest, I was pretty disappointed with my findings. Entity Framework 3.5 is pretty intrusive. All data objects had to either impliment an EntityFramework interface or had to be a subclass of an EntityObject class.
I never went back and revisited that blog post, mainly because I did not want to spew vile about the product; so I just let it be and started looking into nHibernate. I was sort of down because all the good tools like LightSpeed cost money.
Well now it looks like Microsoft has heard our gripes about the products short comings and is going to do something about it.
You can read all about it here.