[11.0 P1] Blazor Web can use BasePath component instead of <base href="">

[ilonatommy]

Doc changes proposal for dotnet/aspnetcore#64590.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/host-and-deploy/app-base-path.md	aspnetcore/blazor/host-and-deploy/app-base-path

[guardrex]

Thanks @ilonatommy! This is great content. I made a handful of suggestions.

We also need a versioned entry for the component with cross-link at ...

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/components/built-in-components.md

I'll search the repo for specific instances of the <base> tag to see if other changes are needed.

Also ... by "stash" I think you mean until the preview lands. Which preview is this for? I still need to set up the 11.0 doc tracking. I'll make sure this is tracked when I set that up.

[guardrex]

@ilonatommy ... I checked ... and Yes! ... it seems that we'll need a round of small changes to address this in other places where the <base> tag (in the host page) is directly referenced. To not bog you down in that grunt work, I'll open a follow-up issue and adjust those cases separately. I'll ping you on that PR for review.

[guardrex]

@wadepickett @tdykstra ... It's that time again! 😆 ........

Invalid moniker range: '>= aspnetcore-11.0'. Moniker 'aspnetcore-11.0' is not defined.

[ilonatommy]

@wadepickett @tdykstra ... It's that time again! 😆 ........

Invalid moniker range: '>= aspnetcore-11.0'. Moniker 'aspnetcore-11.0' is not defined.

There's no hurry, it's just an early draft so that we don't forget about it when the feature gets merged.

[guardrex]

Which preview will this be for?

... and I track with links to the PU issue/PR. I'll see if I can find them if you don't have them handy.

[ilonatommy]

Which preview will this be for?

We're targeting p1.
PR: dotnet/aspnetcore#64590
issue: dotnet/aspnetcore#6818

[guardrex]

LGTM ... will hold now until P1 ships, and I'll get this into the new release notes. I'll probably be the one setting up release notes just because we'll have early Blazor coverage.

@wadepickett or @tdykstra will probably take care of the 11.0 moniker soon.

I've opened #36429 to address the last updates for this.