title: Newbie ASP.NET MVC 5 Model stored procedure heavy backend advice
body: <p>I've got an enterprise app that relied heavily on stored procedures for business logic. I'm thinking about redoing the front end from Webforms to ASP.NET MVC but I'm hoping I don't have to write a model for each stored procedure (there are hundreds). Often times the "Get" stored procedures do not have the same parameters as the equivalent "set" stored procedures do and often times a single stored procedure is updating multiple database tables.</p>
  
  <p>So my question is what is the best practice for building an ASP.NET MVC app on this kind of back end?  Will entity framework work for this?  I'm sure hoping I don't have to build 100's of models, one or two for each stored procedure...</p>
  
  <p>I'm also looking into just using plain razor web pages with webdata's dynamic data row model it might be a better fit. But then I can't use neat things like Kendo UI so much (I think).</p>
  
  <p>Thank you for your wisdom in advance.</p>