repository-pattern

I am getting this error message which when trying to inherit from my GenericRepository. The error says I need to also provide a context but I am not sure how? //IncidentRepository public class IncidentRepository : GenericRepository<Incident> //Generic Repository (to inherit from) public class GenericRepository<TEntity> where TEntity : class { internal db_SLee_FYPContext context; internal DbSet<TEntity> dbSet; public GenericRepository(db_SLee_FYPContext context) { this.context = context; this.dbSet = context.Set<TEntity>(); } EDIT: Just to check I've grasped this? public class

What would a skeleton design look like for a repository able to support multiple database layers using ASP.NET MVC and C#? I want to see what a design would look like if I support both LINQ to SQL and NHibernate. How would I create my database object, and call a method on it in my BLL layer? The repository pattern is probably the best solution for this. You would define an interface for each repository, then create concrete repositories for Linq2Sql and NHibernate implementations, e.g. public interface ICustomerRepository { Customer GetCustomer(int id); } public class NhibCustomerRepository :

I have some e-commerce code that I use often that uses Linq To SQL for saving orders to the database. I want to remove the tightly coupled Linq to SQL bit and pass in an IRepository instead but I am still a little confused on things. Say I have a GetCustomer() method on my ICustomerRepository that returns a Customer object. Do I need it to really return an ICustomer object that gets passed back from that method so if I switch from Linq To SQL to say SubSonic it's not a problem? I believe I do, if that is the case is there a way in Linq To SQL to easily convert my Linq To SQL Customer object to

I am building an MVC app using the Service Layer/Repository/Unit of Work pattern with EF4. I am a bit confused on the logic. I know the point is to decouple the system, but I am a little confused. So the MVC Controllers call on the Services to fill the View Models. So is it safe to say the MVC App is coupled to the Service Layer? Then the Service Layer calls on the Repository to get and persist objects. Is then safe to say the Service Layer is dependent to the Repository? The Repository the utilizes EF4 to get and persist data to SQL server, so I would assume the Repository depends on EF4

Can anyone confirm the best way to integrate the repository pattern with webservices.... Well actually i have my repository patter working now in c#. I have 3 projects, DataAccess, Services and my presentation layer. Problem is my presentation layer is a number of things... I have a ASP.NET MVC site, I have an WPF application and we are about to create another site + an external company needs access to our repository also. Currently i have just added the services layer as reference to each of the sites... But is not the normal way to provide data access via web services? (WCF) - if this is the

I am working on e-tier architecture within MVC framework (ASP.NET MVC5, Entity Framework 6). My application is divided into three sub-projects which are Business-Layer, Data-Access-Layer, Repository (This include repository and Unit of Work) and ASP.NET MVC web-app. I am struggling to understand mapping between business data and entity framework model. for example if I have model class User in entity framework as DAL - User Model [Table("User")] public class User { public User() { } [Key] public int UserID { get; set; } [StringLength(250)] [Required] public string FirstName { get; set; }

In my ASP.NET MVC app, I have a fairly complex edit page which combines a number of models into one view. I'm using the ViewModel pattern to combine all of this information and present one cohesive object to the View. As an example, my ViewModel structure is something like this: CompanyId CompanyName List<Employee> Employees List<ContactMethod> ContactMethods The Employee object has a number of basic properties, and a preferred contact method. On the edit page, the user is given all of the employees of the company and they have the ability to add and remove (using javascript), as well as edit