Home/ Questions/Q 7746975
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-01T10:24:58+00:00

My title sums this up pretty well. My first though it to provide a

  • 0

My title sums this up pretty well. My first though it to provide a few data formats, one being HTML, which I can provide and consume using the Razor view engine and MVC3 controller actions respectively. Then, maybe provide other data formats through custom view engines. I have never really worked in this area before except for very basic web services, very long ago. What are my options here? What is this Web API I see linked to MVC4?

NOTE: My main HTML app need not operate directly off the API. I would like to write the API first, driven by the requirements of a skeleton HTML client, with a very rudimentary UI, and once the API is bedded down, then write a fully featured UI client using the same services as the API but bypassing the actual data parsing and presentation API components.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I had this very same thought as soon as the first talk of the Web API was around. In short, the Web API is a new product from the MS .NET Web Stack that builds on top of WCF, OData and MVC to provide a uniform means of creating a RESTful Web API. Plenty of resources on that, so go have a Google.

    Now onto the question..

    The problem is that you can of course make the Web API return HTML, JSON, XML, etc – but the missing piece here is the Views/templating provided by the Razor/ASPX/insertviewenginehere. That’s not really the job of an “API”.

    You could of course write client-side code to call into your Web API and perform the templating/UI client-side with the mass amount of plugins available.

    I’m pretty sure the Web API isn’t capable of returning templated HTML in the same way an ASP.NET MVC web application can.

    So if you want to “re-use” certain portions of your application (repository, domain, etc), it would probably be best to wrap the calls in a facade/service layer of sorts and make both your Web API and seperate ASP.NET MVC web application call into that to reduce code.

    All you should end up with is an ASP.NET MVC web application which calls into your domain and builds templated HTML, and an ASP.NET Web API application which calls into your domain and returns various resources (JSON, XML, etc).

    If you have a well structured application then this form of abstraction shouldn’t be a problem.

    • 0