blazor web app signalr configuration error

[pigwing]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/server?view=aspnetcore-8.0#signalr-configuration

is not working,by debugging the source code,i found that

need to add circuit property

that is working

https://github.com/dotnet/aspnetcore/blob/9719821d5bb09c7cf75f82a223e8b210da65aaca/src/Components/Web.JS/src/Platform/Circuits/CircuitStartOptions.ts#L14C46-L14C53

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

8.0.100-rc.2.23502.2

Anything else?

No response

[MackinnonBuck]

In Blazor Web apps (i.e., Blazor apps using blazor.web.js), the object passed to Blazor.start() has a slightly different structure due to the fact that both Blazor WebAssembly and Blazor Server can be configured:

Blazor.start({
  ssr: {
    // SSR options here
  },
  circuit: {
    // Circuit (Blazor Server) options here
  },
  webAssembly: {
    // WebAssembly (Blazor WebAssembly) options here
  },
});

@guardrex I thought we had documented this change somewhere in the docs, but now I'm having trouble finding it 🤷 We might want to update the docs to show this new structure by default. Maybe we could use a table where users can toggle between viewing the "Blazor Web" and "Blazor WebAssembly"/"Blazor Server" versions of each snippet?

[guardrex]

@MackinnonBuck ... We've only documented disableDomPreservation thus far. I'll get this on the tracking issue and take care of it as soon as we get the migration/integration guidance finished, which could be later today.