From 438b7390f6cde17ffed1fbbdbeda3a55cef3d314 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Wed, 9 Oct 2019 17:08:31 -0500 Subject: [PATCH] Apply code fencing to Router element in example (#14954) --- aspnetcore/blazor/routing.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/aspnetcore/blazor/routing.md b/aspnetcore/blazor/routing.md index 7c746e24f3ca..9424b439fd60 100644 --- a/aspnetcore/blazor/routing.md +++ b/aspnetcore/blazor/routing.md @@ -5,7 +5,7 @@ description: Learn how to route requests in apps and about the NavLink component monikerRange: '>= aspnetcore-3.0' ms.author: riande ms.custom: mvc -ms.date: 09/23/2019 +ms.date: 10/09/2019 uid: blazor/routing --- # ASP.NET Core Blazor routing @@ -79,11 +79,13 @@ The content of `` tags can include arbitrary items, such as other inte Use the `AdditionalAssemblies` parameter to specify additional assemblies for the `Router` component to consider when searching for routable components. Specified assemblies are considered in addition to the `AppAssembly`-specified assembly. In the following example, `Component1` is a routable component defined in a referenced class library. The following `AdditionalAssemblies` example results in routing support for `Component1`: +```cshtml