>Thank you. I always thought that I need to create a small DB and then do the EF from the existing database (since ultimately I will need to apply the EF to my existing database). But I am sure you know this technology better.
>
>>No, not really. You can forget about all the diagramming, etc. Use EF Code First (the default for MVC). Do the MVC Music Store walk-through http://www.asp.net/mvc/tutorials/mvc-5/introduction/getting-started. You'll get enough EF to get you going.
>>
>>Now, when you get to doing a real system with an existing DB, come back and find out how to make Code First bring in an existing DB.
>>
>>
>>>I agree that learning on a small project is a better approach. But as you say "a small MVC app using EF" which implies that I need to know some basics about EF. And so far, I can't get my mind around it (EF). Or - probably more honest answer - didn't spend uninterrupted time learning.
>>>Thank you.

This tutorial took me about 4 hours.
It handles most of the things that Craig mentions.


http://www.asp.net/mvc/tutorials/getting-started-with-ef-using-mvc/creating-an-entity-framework-data-model-for-an-asp-net-mvc-application