The routing engine is responsible for mapping the incoming requests to the appropriate action method of the controller.

We should have route names as it gives the route a logical name so that the named route can be used for URL generation. This greatly simplifies URL creation when the ordering of routes could make URL generation complicated. Routes names must be unique application-wide.

Route names have no impact on URL matching or handling of requests; they are used only for URL generation. Though URL generation is a different topic to study, we can say briefly that we use it for generating links from one page to another in our views.

In the Configure method of the Startup class, we have mapped the following route:

app.UseMvc(routes => 
{
  routes.MapRoute(
    name: "default",
    template: "{controller=Employee}/{action=Index}/{id?}");
});