Some controllers call multiple service write actions, breaking UnitOfWork pattern

[jcii]

[ There is greater shame here ]

The Dispose method in machete's unitofwork has always been broken. This is reflected in memory usage, which has been ignored because #features and #life.

The UnitOfWork pattern has been fixed, but now sins are clear. There are instances of Controllers making multiple service write calls and throwing disposed context exceptions.

Known controllers are:

• [x] WorkAssignmentController.Edit
• [x] WorkerController.Initialize
• [ ] WorkerController.UpdateImage
• [x] WorkOrderController.Create
• [x] WorkOrderController.Edit

This logic needs to be pushed into the service layer where UoW is controlled. This is expected to permit context disposal to work and memory usage to improve considerably.

[jcii]

searched machete.web/*Controller.ts for if

[jcii]

https://msdn.microsoft.com/en-us/library/ff660872(v=pandp.20).aspx https://ayende.com/blog/3955/repository-is-the-new-singleton https://github.com/mehdime/DbContextScope http://mehdi.me/ambient-dbcontext-in-ef6/