Matt Parker

Is it just me or does Blazor hot reload via dotnet watch feel way faster with the latest SDK? (9.0.300)

Java’s Top level statements
openjdk.org/jeps/495
At this point, Java should just fork C# 😅

TaskCancelledException is swallowed in Blazor WebAssembly · Issue #41674 · dotnet/aspnetcore Is 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...

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

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

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

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

Awesome!

It appears Microsoft is investing in performance improvements for MSBuild and the .NET SDK - looking forward to .NET 10!