My intention is the following: I would like to have inside wwwroot a login page with very basic UI (just two texboxes and a button) with plain html + js + css. As soon as this page is loaded (document.onloadI guess) it starts asynchronously the downloading of the assemblies. When the user click the button to login it commit an ajax call to a API for authentication (json web token returns in response if credentials are valid). If the wasm files are already downloaded, the Blazor WASM appears. If the files are not yet downloaded, it wait until are downloaded and the Blazor WASM appears.

I am using the new Blazor 8 (.net 8.0) WebApp template with Identity Authentication and Server & WebAssembly interactive render modes.

I am getting the following error in console:
Error: [MONO] * Assertion at /__w/1/s/src/mono/mono/metadata/assembly.c:1673, condition `<disabled>' not met

I am getting the following error in console:
Error: [MONO] * Assertion at /__w/1/s/src/mono/mono/metadata/assembly.c:1673, condition `<disabled>' not met

I have a Blazor component that needs to get data via the API, the problem is I call fetch API in OnInitializedAsync function, so every time I render the component the fetch API will call.

I have a simple page in my .NET 8 Blazor Client project (see code below).

I have a simple page in my .NET 8 Blazor Client project (see code below).

When I create a new Blazor solution using .NET 8, enabling webassembly, I get two projects, Client and Server.

I have a WebAssembly Blazor app and I want the URLs in my menu to be relative to the current path.
If I navigate to /demo/ and I click on a link with an href of games, I want it to navigate to /demo/games but instead, it treats the href as being absolute and navigates to /games.

We have a REST API that is used by our Blazor spa application which exposes a feature to initiate an oAuth handshake against some line of business system for the purpose of obtaining an access token and ultimately accessing data. Some of these third party systems, can at times, have somewhat of a non-standard oAuth implementation and require additional headers or query parameters. As such the API builds the 302 response which we send back to the Blazor client. Forgive my ignore here as I am not a front-end developer but is it possible within Blazor to capture the 302 response and pop this open into a new browser tab? Upon searching for an answer it seems there’s a way to JS Interop to pop a tab and navigate to a URL but this isn’t what I want. I want the API to return a 302, with say 4 additional headers, and pass that response to the new browser tab?