MVC3 and WebService objects as models
Posted on 2012-09-20
I am on a project that is considering tightly binding a Razor Page (cshtml file) to a web service object. And I have been told to find out if there are any pitfalls to this approach.
In my past MVC projects, I have create a View Model as a POCO class, and used Data Transfer Objects to transfer values from the POCO to the back end methodology, with that's to a backend DLL, a Web Service or Entity Framework. But here the suggestion is to strongly type the model with the object.
Does any see any problems with that approach?
I need to dig into the exception handling plans for that, in the event the web service is not reachable.
Any other problems that anyone sees?