How to disable WebSocket fallback in .NET 9 Blazor App project? #60453
Unanswered
KieranDevvs
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ive created a new Blazor app from the VS templates in .NET 9 (render mode WASM) and the behaviour out of the box is that if the client doesn't have the WASM binaries then it will initially fallback to a WebSocket connection, download the binaries in the background and then switch the rendering over to the client.
I don't want this behaviour but I do want to use .NET 9 features for things like DI constructor injection.
How do I serve just the static WASM files (without a websocket/signalR fallback) and show the user a loading indicator as previously done?
Thanks,
Kieran.
Beta Was this translation helpful? Give feedback.
All reactions