I believe it is an artefact of wanting to enable SPA (Single Page applications). That is, a web app, using mostly a single page, comprised of a lot of javascript calls to a WebApi backend.
It will be rationalised soon enough I believe. - Glav From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Friday, 1 February 2013 9:39 AM To: ozDotNet Subject: New Web API project I thought I'd generate a fresh Web API project from the template to see what it looks like, and I eventually find it under ASP MVC 4. I do so and get 143 files in 20 folders. There are scripts, images, cshtml files, style sheets and lord knows what. What is all this sh*t just to make a http service? I expected to get a concise little project with some skeleton files but I get this gigantic schmozzle. Are you telling me that a Web API project is wrapped-up inside the circus of the ASP MVC framework? Am I expected to delete all the irrelevent files and strip it back to a simple service without a UI, or is there a simpler way of creating a Web API project from scratch? Greg P.S. Silverlight still works best with WCF. You could make http requests from Silverlight, but it's all typeless. I'm not sure if there is some trick to make them work together more pleasantly.
