By: Nick
On the right tracks with not posting domain entities. I don’t believe you want that logic in the controller and I’m certain you want to avoid TryUpdateModel – which isn’t good for testing. Have a look...
View ArticleBy: JJ
I agree with Nick, the controller has too much responsibility. The decision whether to update or create should be made further down the stack.
View ArticleBy: Steve Py
One of the focal points I have with MVVM is that my view-model may be aware of the model, but the view never binds directly to a model. The main reason for this is so that the VM is responsible for...
View ArticleBy: Derek Woolverton
Just for my understanding, did you mean TryUpdateModel(patient); or TryUpdateModel(form); Just trying to follow where form routes to.
View ArticleClik here to view.
By: Anonymous
I meant as I wrote it Any post with an idPatient in the form values will route to this action. TryUpdateModel will update the patient (coming from the repository) with matching fields in the form field...
View ArticleClik here to view.
