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.
Reading about both Linq to SQL and Entity Framework I have developed the impression that EF is more suitable for apps that get data from multiple data sources.
But as I am reading about MVC2 models I see an example where EF is more loosely coupled with your data model.
If I have to add or remove some columns from a table then what is involved in updating my model or DAL with each of these implementations?
EF4 is the way to go. The mappings are no longer completely volatile so you can refresh them with database changes instead of recreating them. Linq to SQL and EF1 are more volatile.