Routing

Goal

This snapshot advances Ironwharf Gazette by teaching you to organize Blazor component routes with MapRazorComponents.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder.

Prerequisites

Use .NET 8 SDK, a terminal, and Docker for Postgres stages. You should recognize C#, HTTP verbs, and basic HTML.

Port 5081 must be free. Copy .env.example and review appsettings.json before database stages.

• .NET 8 SDK
• A code editor and terminal
• Docker from part 4 onward

Concepts

Blazor SSR maps @page directives to URLs. MapRazorComponents wires the App root and Routes router.

Keep components focused: Razor components present data, form handlers and EF Core enforce rules, and Blazor escapes output by default.

Walkthrough

Add home, about, and health endpoints; register Razor components in Program.cs.

Read the example, then open the matching snapshot. The repository includes the surrounding setup and error handling.

builder.Services.AddRazorComponents();
app.MapRazorComponents<App>();

Run and verify

Enter 02-Routing, restore packages, and run on port 5081.

Open http://127.0.0.1:5081. Watch the terminal for validation and database errors.

git clone https://github.com/michaeldunga1/fcc-blazor-blog.git
cd fcc-blazor-blog/02-Routing
cp .env.example .env
dotnet restore
dotnet run --urls http://127.0.0.1:5081

Troubleshooting

A missing MapRazorComponents call leaves component routes undefined. Check both path and @page directives.

Restore errors usually mean the SDK is missing or you opened the wrong folder. For Postgres failures, confirm Docker is running and the ironwharf_NN database name matches the snapshot.

• Read the first error first
• Restart after environment changes
• Never commit .env or production secrets

Try this

Add a /contact component route.

Test a happy path and one invalid or unauthorized request.

• Make one small change
• Test it in the browser
• Compare with the next snapshot only after it works