Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] IJSUnmarshalledRuntime is obsolote in .NET 7 #14

Open
Ksdmg opened this issue Mar 5, 2024 · 3 comments
Open

[Bug] IJSUnmarshalledRuntime is obsolote in .NET 7 #14

Ksdmg opened this issue Mar 5, 2024 · 3 comments

Comments

@Ksdmg
Copy link

Ksdmg commented Mar 5, 2024

I have a .NET 7 project running blazor server side.
When initializing the JSRuntime, an exception is thrown:

await FFmpegFactory.Init(Runtime); // throws System.InvalidCastException: 'Unable to cast object of type 'Microsoft.AspNetCore.Components.Server.Circuits.RemoteJSRuntime' to type 'Microsoft.JSInterop.IJSUnmarshalledRuntime'.'

I found this -> https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/javascript-interoperability/import-export-interop.md#obsolete-javascript-interop-api

@BigBang1112
Copy link

It also seems to be completely removed in .NET 9.

@sps014
Copy link
Owner

sps014 commented Oct 21, 2024

I will mostly rewrite the current js interop code after .NET 9 RC2 release, hopefully they have some news regarding .net wasm threads.

@BigBang1112
Copy link

BigBang1112 commented Oct 21, 2024

I've been roughly following where the new Blazor goes and I think they delayed multithreading once again (like they delay half of the features as usual), and looking deeper it is indeed the reality: dotnet/aspnetcore#17730 (comment)
(which is funny when I look into the readme history)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants