[tillig]

Fixes #117.

Why

The page was written against .NET 5 and said so out loud: "This example for WebAssembly works as of March 30, 2021 with .NET 5." It framed Blazor as "two hosting models," which predates the Blazor Web App and render modes, and left a dangling Example: where a sentence had been split.

A broken link that -W cannot catch

`ASP.NET Core 3 <aspnetcore>`_

That's external-link syntax with a relative target, so docutils treats aspnetcore as a URI and emits:

<a href="aspnetcore">ASP.NET Core 3</a>

An extensionless relative link that 404s. The markup is perfectly valid RST, so Sphinx has nothing to warn about — it's only visible in the output. Now a :doc: reference, resolving to aspnetcore.html.

This is the second defect class I've hit that a clean build can't detect, after the nested inline markup on #204. As with that one, I scanned every page for it rather than fixing the single instance: `text <target>`_ where the target has no URI scheme. One instance existed, this one. Both scans now run before I push.

Reorganized by what decides the answer

The page is now structured by where the code runs, because that's what determines the wiring — not by hosting model:

• Server-side Blazor, and the server project of a Blazor Web App, are ordinary ASP.NET Core hosting, so the page points at the ASP.NET Core guidance rather than restating it.
• WebAssembly needs WebAssemblyHostBuilder.ConfigureContainer, because there is no Host property to attach a service provider factory to. That's the actual reason the two differ, and it wasn't stated.

Two things added that a reader can act on

A Blazor Web App with WebAssembly interactivity has two projects, so two containers. Registrations made in the server project are not visible to components rendered on the client, so anything both sides resolve has to be registered in both. That's the kind of thing you otherwise discover through a confusing runtime failure.

WebAssembly publishes with trimming enabled, which is a problem for a container that locates constructors by reflection. Points at the trimming page rather than duplicating it.

Verification

Both AutofacServiceProviderFactory constructors were checked against source — the existing sample's use of the configuration-action overload was correct, so it's kept rather than churned. There's no Blazor project in the Examples repo (checked), so no example link to add.

sphinx -b html -W --keep-going, doc8, pre-commit clean. Nested-markup and bad-link scans clean across all pages. Rendered HTML checked, including confirming the repaired reference now emits aspnetcore.html.