Blazor SignalR Client

Same Code working on Blazor Server side for a simple Chat, doenst work on Blazor Client side. Just calling the “app” getting several errors in F12 command like

WASM: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.DllNotFoundException: libc assembly:<unknown assembly> type:<unknown type> member:(null)

as I can not debug (also shift alt D in chrome) my guess is happens here protected override async Task OnInitAsync() { connection = new HubConnectionBuilder() .WithUrl(“https://signalrdemo2220190428112854.azurewebsites.net/ChatDemoHub”) .Build(); await connection.StartAsync();

<PackageReference Include="Microsoft.AspNetCore.Blazor" Version="3.0.0-preview4-19216-03" /> <PackageReference Include="Microsoft.AspNetCore.Blazor.Build" Version="3.0.0-preview4-19216-03" PrivateAssets="all" /> <PackageReference Include="Microsoft.AspNetCore.Blazor.DevServer" Version="3.0.0-preview4-19216-03" PrivateAssets="all" /> <PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="3.0.0-preview4-19216-03" />

[danroth27]

@mattferderer No trouble at all 😄

WebSockets support has already been implemented for mono.wasm: https://github.com/mono/mono/issues/9567.

To enable this support in Blazor we need to move to the mono bindings. We’ve been tracking that internally, but I just filed https://github.com/aspnet/AspNetCore/issues/10489 to track it on GitHub.

[danroth27]

We’re getting close. There’s still some work to do on the .NET runtime side to make sure all the .NET Standard APIs used by the .NET SignalR client are supported and functioning appropriately. This should happen as part of the upcoming Blazor WebAssembly release.