-
Notifications
You must be signed in to change notification settings - Fork 18
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
Comments
It also seems to be completely removed in .NET 9. |
I will mostly rewrite the current js interop code after .NET 9 RC2 release, hopefully they have some news regarding .net wasm threads. |
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) |
Closing this as I have removed IJSUnmarshalled API from source. |
I have a .NET 7 project running blazor server side.
When initializing the JSRuntime, an exception is thrown:
I found this -> https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/javascript-interoperability/import-export-interop.md#obsolete-javascript-interop-api
The text was updated successfully, but these errors were encountered: