State Initialize called twice

It looks like the State is Initialized twice when a BlazorStateComponent is the opening page.

Steps to test with with the Blazor Counter example:

1. Put a break-point on the Initialize method of the CounterState class.
2. Run the app and select the Counter page. The app will break once on the Initialize method.
3. Refresh the page (stay on the Counter page).
4. The app will break twice on the Initialize method.

My workaround is a Loaded logic on the MainLayout.razor component:

    bool Loaded { get; set; }
    protected override void OnAfterRender(bool firstRender)
    {
        if (firstRender)
        {
            Loaded = true;
            StateHasChanged();
        }
        base.OnAfterRender(firstRender);
    }

No BlazorStateComponents are loaded until the Loaded flag is true.

[Herdubreid]

The downside of replacing ServerPrerender with Server is the blank page until it’s rendered – this might only be milliseconds but enough to strike you with the thought of something’s wrong .

My workaround shows the loading icon, which could be expanded to a splash page.

[mrpmorris]

If you don’t need prerendering you can change it in /Pages/_Host.cshtml

Replace ServerPrerendered with Server