Enterprise MVC Application Project Setup With Entity Framework

Question

So I was looking at this site which shows a pseudo project setup for entity framework. I know this article does not use MVC but it did get me thinking. Would you guys have your "model" tier to include all of the Entity Framework references, entities, business rules, repository facade, interfaces, buddy classes for validation, and the design model too? Feels a bit bloated. Would you extract any of that to an "Infastructure" tier?

Answer 1

Only if I needed additional decoupling. There is a cost for creating new interfaces to establish new tiers.

If by tier you mean another machine, I certainly don't think you need that.

Within the model "tier" you can always provide additional namespaces, etc. to improve organization.

Answer 2

My "interfacing the model" moments of granduer are on hold for right now. Here is why