Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

By: Mustafa Düman

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

Just a Commit? Let’s forget about repository(since it’s not mentioned in the interface). Is any concrete class implementing a simple commit function be UOW? What will it commit???? Not generic or meaningful at all..

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

public interface IUnitOfWork
{
void RegisterAmended(IAggregateRoot entity, IUnitOfWorkRepository unitofWorkRepository);
void RegisterNew(IAggregateRoot entity, IUnitOfWorkRepository unitofWorkRepository);
void RegisterRemoved(IAggregateRoot entity, IUnitOfWorkRepository unitofWorkRepository);
void Commit();
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

public UnitOfWork() { addedEntities = new Dictionary(); changedEntities = new Dictionary(); deletedEntities = new Dictionary(); } public void RegisterAmended(IAggregateRoot entity, IUnitOfWorkRepository unitofWorkRepository) { if (!changedEntities.ContainsKey(entity)) { changedEntities.Add(entity, unitofWorkRepository); } } public void RegisterNew(IAggregateRoot entity, IUnitOfWorkRepository unitofWorkRepository) { if (!addedEntities.ContainsKey(entity)) { addedEntities.Add(entity, unitofWorkRepository); }; } public void RegisterRemoved(IAggregateRoot entity, IUnitOfWorkRepository unitofWorkRepository) { if (!deletedEntities.ContainsKey(entity)) { deletedEntities.Add(entity, unitofWorkRepository); } } public void Commit() { using (TransactionScope scope = new TransactionScope()) { foreach (IAggregateRoot entity in this.addedEntities.Keys) { this.addedEntities[entity].PersistCreationOf(entity); } foreach (IAggregateRoot entity in this.changedEntities.Keys) { this.changedEntities[entity].PersistUpdateOf(entity); } foreach (IAggregateRoot entity in this.deletedEntities.Keys) { this.deletedEntities[entity].PersistDeletionOf(entity); } scope.Complete(); } } }

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Hi , I have a really silly question,
since I am newbie to, I wonder about this line :
“var context = builder.Create(connection);”
Is that just to instantiate the context ?
what is the type/class of “builder” ?
Is it a EntityConnectionStringBuilder Class as described in MSDN.
What I have seen in almost all tutorials till now is :
“var context = new MyModel()”
May be this is equivalent and the difference is that in the 2nd case the model is often referenced from another ClassLib project.

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

A common problem with methods that receive an Expression tree like Find, Single or First in your example is that they can not easily be mocked in an unit test with most of common Mocking frameworks out there. I can tell this from experience with previous developments.

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

Comments on: Entity Framework POCO (EF4): Generic Repository and Unit of Work Prototype

Mustafa Düman — Tue, 01 Nov 2011 19:35:00 +0000

Hello,

- i’m looking for “generic repository” and “generic unit of work” interface declerations and concrete implementation of these with EF.

Since i want generic interface, the interfaces must not include anything specific to EF.

Is IObjectSet specific to EF? If so, i think this interface is not generic enough.

2- I think the unit of work interface having just a “commit” function is not generic at all. It’s true just for your implementation logic…

The best UOW interface i’ve met so for is below.

If you can implement these with EF then it would be generic..

Interfaces
————————————————————————
public interface IAggregateRoot
{}

public interface IUnitOfWorkRepository
{
void PersistCreationOf(IAggregateRoot entity);
void PersistUpdateOf(IAggregateRoot entity);
void PersistDeletionOf(IAggregateRoot entity);
}

————————————————————————Concrete UOW implementation ————————————————————————

public class UnitOfWork : IUnitOfWork
{
private Dictionary addedEntities;
private Dictionary changedEntities;
private Dictionary deletedEntities;

————————————————————————

These interfaces are from a book. Samples are freely available. The interfaces are in chapter 7 samples:

http://www.wrox.com/WileyCDA/WroxTitle/Professional-ASP-NET-Design-Patterns.productCd-0470292784,descCd-DOWNLOAD.html)

By: Warren LaFrance

Warren LaFrance — Mon, 29 Aug 2011 17:41:00 +0000

Did you ever get an answer to your question?

By: Efekaptan

Efekaptan — Thu, 11 Aug 2011 00:38:00 +0000

Hi, you can also add an (frequently used) order by function

public IEnumerable GetAllOrderBy(Func keySelector) {
return _objectSet.OrderBy(keySelector).ToList();
}

By: Gavin Luo

Gavin Luo — Wed, 27 Jul 2011 01:50:00 +0000

??????

By: Big D

Big D — Fri, 10 Jun 2011 06:50:00 +0000

You mentioned that you are not keeping a static reference to unit of work…what if the user is work across multiple screens and getting and updating data within those screens?

By: zambak zambak

zambak zambak — Tue, 07 Jun 2011 00:08:00 +0000

Since Entity Framework 4.1 there is allready IObjectContextAdapter…Could we have used

    public class UnitOfWork : IUnitOfWork, IDisposable
    {
        private readonly ObjectContext _objectContext;

        public UnitOfWork(IObjectContextAdapter objectContextAdapter)
        {
            _objectContext = objectContextAdapter.ObjectContext;
        } //ommited for brevity }

and

    public class Repository : IRepository where T : class
    {
        IObjectSet _objectSet;

        public Repository(IObjectContextAdapter objectContextAdapter)
        {
            _objectSet = objectContextAdapter.ObjectContext.CreateObjectSet();
        }

//ommited for brevity }then usage becomes var db = new MyEfCodeFirstContext(); // create context (could be auto wired I guess)

var uow = new UnitOfWork(db); // unit of workvar teamRepository = new Repository(db); // no adapter needed (EF provides one)
var newTeam = new Team { Name = “Da Bears” };Thoughts?ThanksZ….

By: Bass

Bass — Wed, 01 Jun 2011 14:37:00 +0000

Or may be they are different approaches and I am totally going in wrong direction.

Thanks for the explanation

By: Cibrax

Cibrax — Wed, 27 Apr 2011 14:23:00 +0000

By: Jarod Ferguson

Jarod Ferguson — Sat, 26 Mar 2011 20:59:00 +0000

@Yeah CreateObjectSet doesn’t load data

By: Yeah

Yeah — Tue, 22 Mar 2011 18:42:00 +0000

why are you calling CreateObjectSet on every context so you can use it? this is a terrible design. So if I want to work with an POCO mapped to a table with 5 million rows, you are going to load all those rows into memory every time?