πΊοΈ Routing Maps URLs to Controllers
URLs need to go somewhere. Routing maps /api/users to UsersController. Clean, organized, discoverable.
π Attribute Routing
[ApiController]
[Route("api/[controller]")]
public class UsersController : ControllerBase
{
[HttpGet]
public IActionResult GetUsers() { }
[HttpGet("{id}")]
public IActionResult GetUser(int id) { }
[HttpPost]
public IActionResult CreateUser(User user) { }
[HttpPut("{id}")]
public IActionResult UpdateUser(int id, User user) { }
[HttpDelete("{id}")]
public IActionResult DeleteUser(int id) { }
}
π― Conventional Routing
// Program.cs
app.MapControllerRoute(
name: "default",
pattern: "{controller=Home}/{action=Index}/{id?}"
);
// URLs:
// / β HomeController.Index()
// /Users β UsersController.Index()
// /Users/Details/123 β UsersController.Details(123)
// Custom routes
app.MapControllerRoute(
name: "admin",
pattern: "admin/{controller=Dashboard}/{action=Index}/{id?}"
);
// Attribute vs Conventional
// Attribute: More control, self-documenting
// Conventional: Less code, centralized
π‘ Route Parameters
- {id} : Required parameter
- {id?} : Optional parameter
- constraint: {id:int}, {name:alpha}
- catch-all: {*path} (wildcard)
- Route order matters (most specific first)
“Routing maps URLs to actions. Attribute routing is clean and self-documenting. Essential for web APIs.”


