Hi i would try to explain as briefly my dude
now in the web layer you use Using calling a handler in the domain model, and the operation against the data model is done per this request; for exmple you update a vehicle and from the web layer you call Using<UpdateVehicle> and this handler uses
the Vehicle model and the repository for Vehicle.
With this new approach i found that is clear when the application is simple as this but imagine for example this case.
You, for example, update a user with their own address, with a view that is composed with a partial vehicle form and a partial address form, the user controller update method call Using<UpdateUser>.execute() and Using<UpdateAddress>.execute().
The first Execute method makes some modelToEntity transformation without knowledge of the relationship of the address entity "attached to it", loosing the entityFramework context ability to maintain this "automatically"and let you have
a "transaction" point of view.
To avoid this or you should create different Execute methods for each kind of web form taking care of the relationship having only one Using call in the controller, or you should create different models at the domain model that have a direct relationship
with the models you work to have, again, only one call from the controller, or there is another solution to have not so huge number of handlers?