title: New MVC4 project with Webapi contains WebApiConfig and RouteConfig
body: <p>I created a new MVC4 Webapi based project and in the App start folder there are several files.  I noticed in the RouteConfig.cs file</p>
  
  <pre><code>        routes.MapRoute(
              name: "Default",
              url: "{controller}/{action}/{id}",
              defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional }
          );
  </code></pre>
  
  <p>And in WebApiConfig.cs</p>
  
  <pre><code>        config.Routes.MapHttpRoute(
              name: "DefaultApi",
              routeTemplate: "api/{controller}/{action}/{id}",
              defaults: new { id = RouteParameter.Optional }
          );
  </code></pre>
  
  <p>Now from what I can tell they are both doing the roughly same thing, except one uses .MapRoute and the other .MapHttpRoute of which the parameters are slightly different in notation.  Are these two different routes for different aspects on the application?  Do they need to be in both places?  If so/not which takes precedence? </p>
  
  <p>I found 
  <a href="https://stackoverflow.com/questions/15017188/difference-between-usage-of-webapiconfig-cs-and-routeconfig-cs">Difference between WebApiConfig.cs and RouteConfig.cs</a></p>
  
  <p>However all it says is one is for Asp.Net routes and the other is for WebApi routes, but I don't see the difference in usage between the two route types. </p>