>Ummm.. yeah... instructors rarely teach best practices.
>
>How about calling it Models.
>
>>This is actually what our instructor taught us. He created Objects project that contained models, then Data project that contained repository and then the actual Web project. I just followed the same suit. Are you saying it was not a good choice? How should I name the project containing just my models?

But then it may be confused with the Models inside the Web project.

Can you tell me how do you usually structure your MVC project? Do you put EF models into a separate project? If yes, how do you usually name it?