title: Web API in MVC solution in separate project
body: <p>I am creating a new MVC4 project, and research has lead me to believe that communicating from javascript to the server side is better achieved now through web API framework rather than controller actions. Is my understanding correct on this?</p>
  
  <p>I am presuming that I can share all my attributes etc between web API and MVC controllers so on the face it, it does not seem a massive change for me.</p>
  
  <p>When I am setting up applications, I like to split components out in to projects. My plan was to have a MVC project and a web API project. But I have ran in to issues. For example I have ended up with 2 apps as such, separate routing set up etc etc.</p>
  
  <p>So my question is, in a MVC application should the web API framework sit within the same project, or should the web API be separated into a project of its own and work around the issues?</p>