Recently I was looking at an unusual problem where we had to add custom
fields to a view on an ad hoc basis. Not really a problem if it was an
MVC app talking directly to a data source. But mine was over several
REST based services that were talking to a CRM dynamics backend, spread
across multiple domains. Which meant we had to change the data models
through out the system. That's when it occurred to me that we can have
one dedicated field that can store all the ad hoc field data using
JASON or xml and we append it to one of the existing fields. Probably
not the ideal solution, but that's when I came across custom binding for
MVC. I would like to share with you how simple and easy it is to use
custom binding to solve similar issues.
See here for more http://www.codeproject.com/Articles/605595/ASP-NET-MVC-Custom-Model-Binder?msg=4591496#xx4591496xx
See here for more http://www.codeproject.com/Articles/605595/ASP-NET-MVC-Custom-Model-Binder?msg=4591496#xx4591496xx
