Geek Answers Handbook

Considerations for implementing LINQ to SQL or Entity Framework now, intending to use NHibernate later

I have a deadline for the initial release of the client-server application, which will subsequently have many iterative releases.

NHibernate is an ORM of choice, mainly based on reputation and my desire to gain experience with it.

The problem is that I still did not have a chance to raise NHibernate again, and I am afraid that this will lead me to leave the track to step on the deadline. So, I think that now I either use LINQ to SQL or Entity Framework, as I have some experience with it and then when i can, replace NHibernate.

Given this scenario, are there any special considerations I should make when abstracting data access or designing a database schema to prevent big headaches when switching to NHibernate?

edit:

As the message referenced by Asad below, L2S is going to limit me to a class table that can be managed in the first iteration, but I don't want to go that route. Suppose now that future migration from EF to NH.

+7
orm linq-to-sql entity-framework nhibernate
source share
1 answer

The next post will help you understand the difference and problems.

  • NHibernate vs LINQ to SQL

Hope this helps

+2
source share

More articles:


All Articles