If I understood correctly the DbContext of Entity Framework (version 5 code first) give us the functionality of tracking entity changes and coordinating the persistence of these changes. As this sounds a lot like functionality usually associated
with the Unit of Work pattern, I am wondering when the explicit use of Unit of Work in our repositories is warranted. In particular it appears to me that when I use Unity to insure that a only a single DbContext is used by repositories, it appears to
be that the Unit of Work is not needed, or are there situations where it would be needed as it appears this is already obtained via the DbContext
