rockfordlhotka
commented
5 years ago Most of it comes down to the ability (or not) of MVC to map a complex hierarchy of information into a postback, and then to map that into a set of objects on the server.
Even something simple, like a page that displays an "editable data grid" as a list or table in the browser is quite complex to map back into a collection on the server.
This article shows how to do it with Razor pages, and links to another article about how to do it with MVC.
http://www.lhotka.net/weblog/#a4c606e73-f870-450a-9538-1ac48e9fe439
GreggThelen
I've read several blog posts on MVC and CSLA. I've found ways to map a singleton object and a list object in this environment.
I've not seen an example of root objects which may contain child objects, or even, child collections.
Perhaps complicated objects cannot be handled by the CslaModelBinder, which is fine, but then I have to wonder what strategy people use in these circumstances. For example, in one blog post Rocky suggested loading the object into memory and then changing the properties manually which would leave the object in an edited state and in a good place for calling an update.
I understand the disconnected nature of the web means that it is necessary to load an object and edit it in the Action handler - I was just hoping for an easy/tested/reliable way to do this with more complex object graphs.
Perhaps I'm asking too much of the technology? Do you just design around this somehow?
Does anyone out there work with MVC and have experience mapping properties more than one level deep?