Post

Matt Parker
@mattparker.dev

Context - working on a blazor app that requires cross origin isolated enabled (running multi-threaded emscripten compiled program in workers, separate to blazor), so no debugging for me - I have to publish the app with `dotnet publish -c Debug`, 1/4

Matt Parker
@mattparker.dev

then serve the files with `dotnet serve -o -S --port 5001 --fallback-file index.html -h "Cross-Origin-Opener-Policy: same-origin" -h "Cross-Origin-Embedder-Policy:credentialless"`. These headers are required if you want to use SharedArrayBuffers. 2/4

Matt Parker
@mattparker.dev

Setting <WasmEnableThreads>true<WasmEnableThreads> does set these headers, but Blazor currently throws on startup with the property set to true. 3/4

0 reposts1 like

Matt Parker
@mattparker.dev

I wish I remembered this github.com/dotnet/aspne... while trying to reason with why long running tasks (interoping with the workers) weren't throwing an OperationCancelledException once I cancelled the CTS. Turns out they were! 4/4

github.comTaskCancelledException is swallowed in Blazor WebAssembly · Issue #41674 · dotnet/aspnetcoreIs there an existing issue for this? I have searched the existing issues Describe the bug When cancelling a cancellation token (using ThrowIfCancellationRequested) neither TaskCancelledException no...