From f5625646b463d55f0ee412e0d75066dd6de94719 Mon Sep 17 00:00:00 2001 From: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com> Date: Fri, 22 May 2020 17:16:21 -1000 Subject: [PATCH] Update routing.md (#18448) --- aspnetcore/mvc/controllers/routing.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/aspnetcore/mvc/controllers/routing.md b/aspnetcore/mvc/controllers/routing.md index 6b430b7f3d..9990951731 100644 --- a/aspnetcore/mvc/controllers/routing.md +++ b/aspnetcore/mvc/controllers/routing.md @@ -272,7 +272,10 @@ The `HomeController.Index` action is run for any of the URL paths `/`, `/Home`, This example highlights a key programming difference between attribute routing and [conventional routing](#cr). Attribute routing requires more input to specify a route. The conventional default route handles routes more succinctly. However, attribute routing allows and requires precise control of which route templates apply to each [action](#action). -With attribute routing, the controller name and action names play **no** role in which action is matched. The following example matches the same URLs as the previous example: +In the following code: + +* The controller name and action names play **no** role in which action is matched. +* Matches the same URLs as the previous example: [!code-csharp[](routing/samples/3.x/main/Controllers/MyDemoController.cs?name=snippet)]