In other contexts, I'm used to "binding" inferring bidirectional movement of the data to/from the object. Put in other terms, we could call the movement of data from an object to a html form 'serialization' and the reverse, 'deserialization'. However model binders and value providers, seems only responsible for populating an object from an http request - the deserializing part. What part of the pipeline is responsible for taking data from the object and serializing it to the form or other http response? Or does it simply stop with the 'Html.TextBoxFor' utility?
I beleive I could create a custom InputExtension but that seems overkill - the default does most of what I need except for when it grabs the value for a property. I could also create a different model but that is also something I'm trying to avoid.
Is there an extensibility point where I could manage the value extraction from the model to the html input?