I am curious about use EF4 ObjectContext at Controller.
I dont have much asp.net mvc projects to use as reference.
Controler -> ObjectContext
Controler -> Repository -> ObjectContext
Controler -> Service -> Repository -> ObjectContext
Sometime I think that repositories are waste of time, just replicating ObjectContext interface. Some people use "GenericRepository<T> where T: Entity" with GetById, Add, Delete and Update....then, why not just reference ObjectContext
directly, its more fast, easy to do, easy to understand. UnitOfWork too...
Services are util sometimes, ie.: Add HistoricalChanges when saving a object.
What you preffer?