repository-pattern

My repositories deal with and provide persistence for a rich domain model. I do not want to expose the anemic, Entity Framework data entity to my business layers, so I need some way of mapping between them. In most cases, constructing a domain model instance from a data entity requires the use of parameterised constructors and methods (since it is rich). It is not as simple as a property/field match. AutoMapper could be used for the opposite situation (mapping to data entities) but not when creating domain models. Below is the core of my repository pattern. The EntityFrameworkRepository class

I have repository generic where I do method as Get,Update,Insert. I get a data from table in data base I use this method. public IEnumerable<typeEntity> Get<typeEntity>(Expression<Func<typeEntity, bool>> newObjectEntity,int page, int rowsByPage) where typeEntity : class { List<typeEntity> Result = null; Result = Context.Set<typeEntity>().Where(newObjectEntity).OrderBy(m => true).Skip<typeEntity>(5 * (page - 1)).Take<typeEntity>(rowsByPage).ToList<typeEntity>(); return Result; } I when get data only a one table this is my code: var collecProducts = repository.Get<Products>(c => true); My

I use EF 4.1 with Repository and DbContext.. POCO with T4 template. For every Repository I use a separate DbContext. I need to update an object with has a related property, at the moment I receive this error An entity object cannot be referenced by multiple instances of IEntityChangeTracker. I suppose my problem is beacuse eventObj and candidate are created from different Repositories. So i'm trying to solve the problem with this code, with no success. My question? How do I get rid of this error? Is is possible remove the candidate from its context? public void UpdateAddingCandidate(Event

In my ASP.NET MVC application, I am using unit of work and repository patterns for data access. Using the unit of work class and the repository defined inside it I am fetching the related set of entities in my controller. With my beginner knowledge, I can think of two ways to fetch the business model and convert it to view model. Repository returns the business model to controller, this model than mapped to view model, or Repository itself converts business model to view model and then it is returned to controller. Currently I am using first approach, but my controller code started to look

New to EF and I have noticed that using a repository pattern can really simplify things and will allow me to do some mocking too.So far so good. My Question A typical usage of the objectContext is to destroy as soon as possible see below using (var context = new SchoolEntities()) { context.AddToDepartments(department); context.SaveChanges(); } Using the Repository pattern I have noticed that nobody actually uses the "Using Pattern" eg using (var repository= new Repository<Student>(new MyContext)) { repository.Add(myStudentEntity) repository.SaveChanges(); } Should the idea be that we should

I feel like I'm running around in circles. I can't seem to make up my mind as to what the right repository pattern is using LINQ to SQL . If you're familiar with Rob Conery's MVC Storefront you will see that his implementation wraps the LINQ-generated models with another class and treats the LINQ-generated one simply as a data transfer object (DTO). It looks something like this: //Custom wrapper class. namespace Data { public class Customer { public int Id {get;set;} public string Name {get;set;} public IList<Address> Addresses {get;set;} } } //Linq-Generated Class - severly abbreviated

I am new to Repository pattern. When I am managing the CRUD operations of several entities (like: customers, orders etc) then its fine. I am making an interface, I am making a Generic repository. And that serves my purpose, because CRUD operation is common for them. My question is: When the duties of several entities are totally different, there is no common method between them, in this case what should I do? Should I increase the number of interfaces and repositories for those specific purposes? Or is there any better solution in terms of best practices? How should I manage Generic Repository