Unit of Work

Sep 6, 2011 at 5:14 AM

 In some real world scenario, a single transaction would be be spanned in multiple repository implementations. So you should not call the UnitOfWork.SaveChanges() method from individual repositories. It would be great if you implement the Unit of Work pattern for handling multiple repository implementations

Developer
Sep 6, 2011 at 5:57 PM

Hi,

Thanks for your feedback. I added a work-item so that the Silk team considers this for future releases.

Agustin Adami
http://blogs.southworks.net/aadami