unit-of-work

Lets say I have 2 tables. ProductCategory and Product . I have 1 generic repository that can handle both tables: public class GenericRepository<T> : IRepository<T> But when using unit of work pattern, am I forced to create a repository for ALL tables in my database? public interface IUnitOfWork : IDisposable { int SaveChanges(); IRepository<ProductCategory> ProductCategoryRepository { get; } IRepository<Product> ProductRepository { get; } } Is there not a way I can add the generic repository to the unit of work class? You can add a generic method to the IUnitOfWork interface: public interface

Having built a small application using the Unit of Work/Repository pattern, I am struggling to understand how to use this properly within my business layer. My application has a a data access layer which can be either NHibernate or the Entity Framework. I can switch between these easily. I have a number of repositories, for example, Customer, Order etc. My unit of work will be either an ISession or an Object Context depending on which DAL I want to test with. My business layer contains a single business method - CreateOrder(). What I am struggling to understand is where in the business layer I

I am trying to update a complex model in a single view. I am using ASP.NET MVC3, Entity Framework with Code first, unit of work, generic repository pattern.. but when I try to update the model, i come up with this error: A referential integrity constraint violation occurred: The property values that define the referential constraints are not consistent between principal and dependent objects in the relationship. Here is my simplified view model: public class TransactionViewModel { public Transaction Transaction { get; set; } public bool IsUserSubmitting { get; set; } public IEnumerable

Im trying to implement an unit of work pattern by passing an unit of work instance into my repositories. Relevant code from Global.asax. public class SiteModule : NinjectModule { public override void Load() { Bind<IUnitOfWork>().To<SqlUnitOfWork>() .InRequestScope() .WithConstructorArgument("connectionString", ConfigurationManager.ConnectionStrings["Entities"].ConnectionString); Bind<IProductRepository>().To<ProductRepository>(); Bind<ICategoryRepository>().To<CategoryRepository>(); } } Repository constructors: public class ProductRepository { IUnitOfWork unitOfWork; public ProductRepository

I'm thinking about starting a new project using EF 4 and going through some articles, I found an article about EF with repository pattern and unit of work ( http://blogs.msdn.com/b/adonet/archive/2009/06/16/using-repository-and-unit-of-work-patterns-with-entity-framework-4-0.aspx ) Looking at that article, it uses the ObjectContext as the UnitOfWork and it passes it to the Repository. My question is what if I have 2 ObjectContext which mean I will have 2 unit of work, but I actually wants all the operation perform on those 2 context to be one single unit of work, is this scenario possible? I

I'm using the " stub technique " to update my POCO's (used in a detached context, ASP.NET MVC). This is the code i currently have in my controller (which works): [HttpPost] public ActionResult Edit(Review review) { Review originalReview = _userContentService.FindById(review.PostId) as Review; var ctx = _unitOfWork as MySqlServerObjectContext; ctx.ApplyCurrentValues("MyEntities.Posts", review); _unitOfWork.Commit(); // ..snip - MVC stuff.. } As you can see, there is code smell everywhere. :) A few points: I use Dependency Injection (interface-based) for basically everything I use the Unit of