Now, the first question should be, why do I need a repository or unit of work pattern at all? Couldn’t I just use the EF context from the controller, having the full power of directly writing the query I need and returning the data? Answer: You could, but the real intent behind is testability and … Read more
I have to say first that there is not a unique right way to solve this issue. I’m just presenting here what I would probably do. First thing is, DbContext itself implements the Unit of work pattern. Calling SaveChanges does create a DB transaction so every query executed against the DB will be rollbacked is … Read more
I have found working with ASP.Net Identity 2.0 and EF6 a bit challenging. The biggest drawback is the lack of documentation or conflicting documentation. I am using WebApi 2.0, EF6 and ASP.Net Identity 2.0. At first it was tough to get going but once it’s working, it’s been good. I created my own Identity classes. … Read more
This Git project is very helpful. I started from the same and did some changes as per my need. public sealed class DalSession : IDisposable { public DalSession() { _connection = new OleDbConnection(DalCommon.ConnectionString); _connection.Open(); _unitOfWork = new UnitOfWork(_connection); } IDbConnection _connection = null; UnitOfWork _unitOfWork = null; public UnitOfWork UnitOfWork { get { return _unitOfWork; … Read more
SQLAlchemy tracks the changes to each attribute. You don’t need to (and shouldn’t) query the instance again in the event. Additionally, the event is triggered for any instance that has been modified, even if that modification will not change any data. Loop over each column, checking if it has been modified, and store any new … Read more
You cannot have partially opened classes (e.g. with UnitOfWork<Repository<>,> you have specified T but not O) inside a typeof, try it with: var builder = new ContainerBuilder(); builder .RegisterGeneric(typeof(UnitOfWork<,>)) .As(typeof(IUnitOfWork)) .InstancePerDependency(); The where T : Repository<O> generic constraint will take care of that the first argument should be an Repository<> But it won’t work with … Read more
Repository can work without Unit Of Work, so it can also have Save method. public interface IRepository<T> { T Get(int id); void Add(T entity); void Update(T entity); void Remove(T entity); void Save(); } Unit Of Work is used when you have multiple repositories (may have different data context). It keeps track of all changes in … Read more
Neat solution, but each instance of LifetimeManager should use a unique key rather than a constant: private string _key = string.Format(“PerCallContextLifeTimeManager_{0}”, Guid.NewGuid()); Otherwise if you have more than one object registered with PerCallContextLifeTimeManager, they’re sharing the same key to access CallContext, and you won’t get your expected object back. Also worth implementing RemoveValue to ensure … Read more
Yes, DbContext represents a Unit of Work and DbSet represents a Repository, but some people will create a layer of abstraction over them. Here are some reasons people might do so: Maybe they don’t want their project tightly coupled to Entity Framework and its architecture. So, they hide Entity Framework behind those abstractions so they … Read more
A way to approach this is to not make the UnitOfWork responsible for creating each Repository through Container injection, but instead to make it the responsibility of each Repository to ensure that the UnitOfWork knows of its existence upon instantiation. This will ensure that your UnitOfWork doesn’t need to change for each new Repository you … Read more