I\'ve just started a new project and have naturally opted to use a lot of new tech. I\'m using (Fluent) NHibernate, ASP.NET MVC 3 and am trying to apply the Repository pattern.
In OOP Design Patterns, what is the difference between the Repository Pattern and a Service Layer? I am working on an ASP.NET MVC 3 app, and am trying to understand these design patterns, but 开发者_
I am fairly new to MVC, but after playing with it (MVC 3/Razor), I am hooked. I have a few questions: 1) What is the best, or most widely used pattern to develop MVC apps in? Repository, DDD, UOW?
Could someone explain the benefits of using this pattern? I mean isn\'t EF a repository in a sense already? Can\'t you just query the container and return those objects?
I have a repository like this public abstract class BaseRepository<TEntity> : IRepository<TEntity> where TEntity : class
I have multiple开发者_运维问答 repositories in my application.Where should I put the ObjectContext?Right now, I have a reference like ObjectContext ctx; in every repository.What is the smartest and sa
Suppose I have a TeacherRepository that needs to make use of a CourseRepository per the code below. Teacher and Course form a many to many relationship. Teacher and Course do not form an aggregate. Wo
Ok, So I have been taking in all sorts of gre开发者_如何学Pythonat information about MVC, EF4, Repository Pattern, UoW, Service Layers, etc and now I am going to attempt to put it all together.
Where do we put the logic for paging and sortin开发者_Python百科g data in an asp.net repository pattern project?
People have yelled at me, that I should always use 开发者_如何学编程the repository pattern, which I\'ve done for quite a while... Now I\'m wondering whether there is any decent alternatives for this p
加载中,请稍侯......