Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Now that Entity Framework 4.0 is coming out I was wondering, if you were planning to use EF 4.0 when it is released would it be easier to go from LinqToSQL to EF 4.0 or EF 3.5 to 4.0?
In other words if you were starting a project now anticipating using EF4.0 would you use LinqToSQL or EF3.5 now?
It will be easier to migrate from EF 3.5, because many parts of the code will be common. It still will be a lot to do, because if I migrated to EF 4.0, I would propably switch to code only design. Why do you limit yourself to EF and Linq to SQL? There are other solutions: Subsonic, nHibernate. They are more mature, thought through and well tested.