Reactive.Wasm for NET10?

[Dunge]

I recently updated everything to ReactiveUI 24.1. A blazor project is configured as mentioned in the doc (https://www.reactiveui.net/documentation/getting-started/installation/blazor/#recommended-project-structure) in the section "For Blazor WebAssembly:" with .WithBlazor()

I was having an issue where a refresh inside an .ObserveOn(RxSchedulers.MainThreadScheduler) call would work in a MAUI version of the app, but not when running under WASM.

AI looked at it and after a while found that I should be calling WithBlazorWasm() instead to take advantage of that Wasm scheduler and it should fix my threadhing issues.

I checked and I do have the latest (Reactive.Wasm (v3.0.1)) referenced via dependency from ReactiveUI.Blazor.Reactive.

But now when I execute my project I receive a "The currently running version of the runtime does not support this version of the WebAssembly scheduler." exception.

So what now? I was only ported up to NET9? What should I use instead?

[Dunge]

Ok follow up. I don't like relying on that damn AI but it seems like a correct answer. It found that:

.WithBlazorWasm() is bugged: it resolves "WasmScheduler.Default" to the OLD, retired System.Reactive.Concurrency.WasmScheduler instead of the intended replacement.

Instead it changed the initialization with:

var wasmScheduler = ReactiveUI.Primitives.Reactive.Concurrency.WasmScheduler.Default;
var rxApp = RxAppBuilder.CreateReactiveUIBuilder()
    .WithMainThreadScheduler(wasmScheduler)
    .WithTaskPoolScheduler(wasmScheduler)
    .WithPlatformModule<ReactiveUI.Reactive.Blazor.Registrations>()

And now it seems to work. Even fixed my UI refresh issue.

Does it look correct? Anything I should be watching out for?

[glennawatson]

Sorry didn't notice, looks reasonable. Yeah we moved most of the concurrency stuff to our own machine Primitives so that makes sense. Will investigation why that WithBlazorWasm isn't resolving to the correct resolver though. Will make a issue and track.

In terms of AI my view it's a tool like any other, used with appropriate supervision it's fine, used like it's a oracle it stops being a tool.

[glennawatson]

Doing a release now that with the fix