Refresh the .NET MAUI Blazor Hybrid templates to align with the .NET 11 updates to the Blazor Web App template

[danroth27]

We should target being done with the template updates for .NET 11 Preview 4.

History of changes so far (ignore the Identity related commits): https://github.com/dotnet/aspnetcore/commits/main/src/ProjectTemplates/Web.ProjectTemplates/content/BlazorWeb-CSharp

This one looks relevant: dotnet/aspnetcore@9dce7ab

[ilonatommy]

Change	PR	Description	Needs Action?
NavMenu: remove inline JS	#63828	Replace inline onclick with collocated JS module	✅ Yes — both templates have inline onclick handler
Error page: PersistentState	#64634	Add [PersistentState] to fix RequestId flashing	✅ Yes — solution Error.razor missing [PersistentState]
BasePath component	#64590	Replace <base href="/"> with <BasePath />	✅ Yes — solution App.razor still uses <base href="/">
ResourcePreloader	#62673	Rename LinkPreload → ResourcePreloader	⏭️ Already applied in solution App.razor
ReconnectModal	#60376	Add reconnect UI component	⏭️ Already applied in solution App.razor
NotFoundPage on Router	#60970	Add NotFoundPage to <Router>	⏭️ Already applied in both templates
Circuit pause/resume	#62549	JS pause/resume circuit APIs	❌ Not applicable — pauseCircuit()/resumeCircuit() are SignalR-only. [PersistentState] is a separate feature that works in Hybrid (registered in AddBlazorWebView).
Accessibility (a11y)	#57125, #57127	aria-labels, hamburger visibility, color-scheme	⏭️ Already applied — aria-labels & color-scheme present
Asset fingerprinting	#56045	Use @Assets[] for CSS/JS refs	⏭️ Already applied in solution; N/A for single (static HTML)
Primary constructors	#59712	Use C# primary constructors	❌ Not applicable — no constructors to modernize
Docker support	#63815	Light up "Add Docker" in VS (ide.host.json flag)	✅ Yes — solution web project's .template.config needs the flag
dev.localhost URLs	#62668	Use *.dev.localhost for dev-cert	⏭️ Already applied in launchSettings.json

[danroth27]

@ilonatommy @mattleibow Can this issue now be closed?

[ilonatommy]

Yes. Doesn't this repo have "fixes" keyword working? #34945 should have closed it.

[danroth27]

@ilonatommy This may not have been closed automatically because it was merged into the net11.0 branch instead of the main branch. I'm not sure what the process is for merging net11.0 into main. @mattleibow?