Routing — Complete Guide

Routing — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of ASP.NET Core Tutorial on Toolliyo Academy.

8 min read Updated 7/8/2026

On this page

ASP.NET Core Tutorial (ShopNest) · Lesson 12 of 100

Routing

Beginner → Intermediate → Advanced → Professional

Beginner · 1 — Foundations · ~12 min read · Module 2: MVC Fundamentals

Introduction

This lesson is part of the beginner section. We explain Routing slowly, with examples you can copy and run. If something is unclear, read it twice — that is how everyone learns. Routing maps a URL to a controller action. Conventional routing uses a pattern like {controller}/{action}/{id}. Attribute routing puts [Route] and [HttpGet] on classes and methods. SEO-friendly URLs (/products/wireless-mouse) and REST APIs (/api/orders/42) both depend on correct routing.

Routing appears in almost every web app you will build. Once it clicks, EF Core and Web API become much easier.

When will you use this?

You use this in every web page and form you build from your first app to production.

Product pages, login forms, and admin dashboards all use controllers, views, and models.
When a user submits an order form, model binding maps form fields to a C# class.

Real-world: Flipkart-style order service

The E-commerce team building Flipkart-style order service uses Routing to map /orders/42 to the correct action method with the right id. customers and warehouse staff never see the C# code — they just get a fast, reliable product catalog and checkout API.

Production-style code

// Conventional — in Program.cs
app.MapControllerRoute(
    name: "default",
    pattern: "{controller=Home}/{action=Index}/{id?}");

// Attribute — on controller
[Route("shop")]
public class CatalogController : Controller
{
    [HttpGet("item/{slug}")]
    public IActionResult Item(string slug) => View();
}

What happens in production: In Flipkart-style order service, getting Routing right means customers and warehouse staff trust the product catalog and checkout API every day.

Lesson example (start here)

Copy this smaller example first. Once it works, compare it with the real-world code above.

// Conventional — in Program.cs
app.MapControllerRoute(
    name: "default",
    pattern: "{controller=Home}/{action=Index}/{id?}");

// Attribute — on controller
[Route("shop")]
public class CatalogController : Controller
{
    [HttpGet("item/{slug}")]
    public IActionResult Item(string slug) => View();
}

Line-by-line walkthrough

Code	What it means
`// Conventional — in Program.cs`	Comment — notes for humans; the compiler ignores it.
`app.MapControllerRoute(`	Middleware or endpoint mapping — part of the request pipeline in Program.cs.
`name: "default",`	Part of the Routing example — read it together with the lines before and after.
`pattern: "{controller=Home}/{action=Index}/{id?}");`	Part of the Routing example — read it together with the lines before and after.
`// Attribute — on controller`	Comment — notes for humans; the compiler ignores it.
`[Route("shop")]`	Attribute — tells ASP.NET Core how to route or secure this class/method.
`public class CatalogController : Controller`	Controller class — handles HTTP requests and returns views or JSON.
`{`	Part of the Routing example — read it together with the lines before and after.
`[HttpGet("item/{slug}")]`	Attribute — tells ASP.NET Core how to route or secure this class/method.
`public IActionResult Item(string slug) => View();`	Return type — can be a view, redirect, JSON, or error response.
`}`	Closes a block started by { above.

How it works (big picture)

Optional id?
means id can be omitted.
Attribute routes stack on the controller prefix — /shop/item/keyboard.

Do this on your computer

Add a route with id and open /Products/Details/3.
Add [Route] on one controller and test the new URL.
Use dotnet run and fix 404s by reading the route table in logs.
Read the real-world section and name which part of the app uses this topic.
Run the example locally with dotnet run and confirm the same behavior.
Change one value in the example (route, text, or connection string) and predict what will happen before you save.

Experiments — try changing this

Change a string or route in the example and save — watch the browser or Swagger response update.
Break the code on purpose (remove a semicolon), read the error message, then fix it.
Change the URL path and update the browser address to match.

Remember

Conventional routing = global pattern. Attribute routing = explicit URLs on actions. Order and uniqueness matter.

Common questions

API routing?

Web API uses [Route("api/[controller]")] on ControllerBase classes.

How long should I spend on Routing?

Until you can explain it in your own words and run the example without looking at the answer. Beginners often need 30–60 minutes per new concept; setup lessons may take one afternoon.

What if I get stuck on Routing?

Re-read the line-by-line walkthrough, check the terminal for red errors, and compare your code character-by-character with the example. Search the exact error text — someone else had it too.

Where is Routing used in real jobs?

See the real-world section above — the same pattern appears in LMS, banking, e-commerce, and SaaS backends. Interviewers ask you to explain it using one concrete example.

Questions on this lesson 0

No questions yet — be the first to ask!