Blazor webassembly does not initialize components in the LayoutComponentBase after webassembly resources downloaded.

[IvanDmitriev1]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When blazor has downloaded all webassembly resources, it initializes, but also forgets to initialize components that have @rendermode="@RenderMode.Auto". This will not happen if the resources are already cached.

Expected Behavior

Blazor should initialize all component that have RenderModeAuto or @rendermode="@RenderMode.Auto".

Steps To Reproduce

I have create a repository for this issue: https://github.com/IvanDmitriev1/BlazorIssue

1. Navigate to the index page
2. Clear site cache (if it's not first loading)
3. Reload page
4. Navigate to the dialog page and click on Open Dialog button
5. An error will occur because DialogProvider that is in MainLayout isn't initialized

Exceptions (if any)

No response

.NET Version

8.0.100-rc.2.23462.28

Anything else?

.NET SDK:
Version: 8.0.100-rc.2.23462.28
Commit: 5e71ffbd44

Runtime Environment:
OS Name: Windows
OS Version: 10.0.22621
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\8.0.100-rc.2.23462.28\

.NET workloads installed:
There are no installed workloads to display.

Host:
Version: 8.0.0-rc.2.23431.9
Architecture: x64
Commit: 3c48925a6c
RID: win-x64

.NET SDKs installed:
6.0.414 [C:\Program Files\dotnet\sdk]
7.0.401 [C:\Program Files\dotnet\sdk]
8.0.100-rc.2.23462.28 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.0-rc.2.23455.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.0-rc.2.23431.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.22 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.0-rc.2.23454.1 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

[SteveSandersonMS]

I think this is the same issue as described at #50686. That is, you have this in your layout:

<DialogProvider @rendermode="@RenderMode.Auto" />

... so it initially resolves as Server. Since it never gets removed from the page, it continues to use Server. Then when you later visit Dialog.razor (which also has RenderModeAuto), the rendermode for the page resolves as WebAssembly. Since there are different hosting platforms, they aren't sharing the same DI services, and hence it fails.

I'll close as a duplicate of #50686 but please let me know if you think that doesn't cover it.

@MackinnonBuck Looks like this is further reason to make Auto continue resolving as Server until all the server components are gone.