Thank you for this sample, however I still have some conceptual questions please. It maybe that my knowledge isnt where it should be, but where I am having an issue is same setup as Alan, but I have three separate projects. I have a MVC 5 client app, an OpenAccess Web API service app, and an OpenAccess Model project.
Obviously the OpenAccess Web API has to know about the model and all of that is working perfectly, but where I get lost is on the client side consuming the Web API. In my mind the the client should have no knowledge about the OpenAccess model class, but without a WSDL/Contract to describe the model I am not sure how the client is going to function without knowledge of it. I have poured through the examples dealing with your UI for ASP.NET MVC controls, but they all including this one have a direct reference to OpenAccess Model
Should I actually reference the OpenAccess model project in the MVC client app? That seems to coupled to me, however your controls and your examples all lead me to believe it to be true.
If I am incorrect do you mind providing another sample that shows how your controls can reference the Web API without sharing the OpenAccess project?