Blazor WASM client has become unstable in Large Spa

110 Views Asked by At

I have a fairly large Blazor client WASM application. Things were going great and I hit a wall.

After last week I seem to hit a wall. Things that happen are:

  • Some breakpoints don't work
  • Debug build the server dies, which may be the cause of the above.
  • Console.WriteLines don't work in chrome but seem to in Edge
  • Unexpected Exceptions are thrown on will used services.

I think there is some other weirdness, but don't remember off the top of my head. I am starting to think Blazor WASM isn't ready for prime time.

Has anyone else seen this?

How much data memory to Blazor have access to?

How large can the Blazor WASM code be?

0

There are 0 best solutions below