ED - recommended or preferred DB abstraction?
Posted: Thu 02 Feb 2012 18:28
I have been working with NH for a while now, and the experience has been anything but pleasant.
ED for NH made it more bearable, but I am still having a number of problems, both with NH as such, and with the ED for NH tool, as you can see from my littering the forum with lengthy posts.
Of the three supported database abstractions (Entity Framework, LINQ to SQL, NH) - which would you personally prefer or recommend?
I have no attachment to my existing schema - matching a particular schema or mapping is not a concern, as the application I'm building has not yet been deployed. So backwards compatibility with an existing database is not important.
How does ED for LINQ to SQL compare to ED for NH in terms of features?
ED for NH made it more bearable, but I am still having a number of problems, both with NH as such, and with the ED for NH tool, as you can see from my littering the forum with lengthy posts.
Of the three supported database abstractions (Entity Framework, LINQ to SQL, NH) - which would you personally prefer or recommend?
I have no attachment to my existing schema - matching a particular schema or mapping is not a concern, as the application I'm building has not yet been deployed. So backwards compatibility with an existing database is not important.
How does ED for LINQ to SQL compare to ED for NH in terms of features?