title: Asp.Net Core - MVC Vs WebAPI routing difference
body: <p>This issue might be raised earlier hence can be duplicate.</p>
  
  <p>When we configure ASP.NET core app (MVC) we define and map routes under Startup.cs - Configure - <code>app.useMvc()</code>. And this works perfectly. 
  However,  when WebAPI comes into picture, why we need to specify <code>[Route("api/[controller]")</code>  specifically?  In other way, webAPI only works with attribute routing?</p>
  
  <p>Why can't Configure method handles this route configuration? Which was good option in earlier MVC/WebAPI (not core). </p>
  
  <p>Am I missing anything?</p>