.net - Considerations for implementing LINQ to SQL or Entity Framework now, intending to use NHibernate later -
I have a preliminary release deadline for a client-server application in which there will be a lot of repeated releases.
NHM is the ORM of choice, to a great extent, and my desire to gain experience with it.
The problem is that I still have not got the opportunity to get the NHibernate spike, and I'm afraid that by doing this I'm going to throw me out of the track to get on the deadline. Therefore, I am thinking that I can use the SQL or unit framework from the LINQ now because I have some experience with those , and then when I enable I swap to NHibernate.
Considering this scenario, what should I do to eliminate or design a data layer to prevent major headaches when going to NHibernate?
Edit:
As per the post given below, L2S is going to limit me to table-per-square, which can be manageable in the first run But I do not want to go down that path down Let's assume the future migration of the NH from EF.
The following post
- < / Ul>
Hope this helps
Comments
Post a Comment