Repository.Delete requires a SaveChanges

Related Documentation:
https://aspnetboilerplate.com/Pages/Documents/Unit-Of-Work#automatically-saving-changes

There is an inconsistency with regards to Updating and Deleting an entity.

This is off the latest MVC sample download.

To make a simple example, I just modified the user delete function to also change the name too, to demostrate my point.

Editing a property seems to instantly update it, even if I “re-get” the entity. However, deleting the entity does not instantly update it, as you can see in the image.

Shouldn’t these two things be consistent? Either an update also requires a SaveChanges, or the Delete does not require a SaveChanges.

[acjh]

In unit test, there is no outer unit of work, so SaveChanges is called when UnitOfWorkInterceptor completes the unit of work.

https://aspnetboilerplate.com/Pages/Documents/Unit-Of-Work#conventional-unit-of-work-methods

[ismcagdas]

When updating, you already changed the field values fore calling Update method. For delete and create (for generating Id value for example), SaveChanges must be called.