Replies: 2 comments 3 replies
-
Have you tested this in Blazor, yourself? See this open SkiaSharp / Blazor Wasm issue. It links to a closed issue, which contains a comment with a code snippet that might be relevant.: Perhaps this line:
You could follow the steps (and these issues); get SkiaSharp working with Blazor Wasm. Then compare the resulting csproj to yours. |
Beta Was this translation helpful? Give feedback.
1 reply
-
SkiaSharp and Blazor Wasm has never worked for me :'( |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a Wasi Console App (.NET 9, preview 6) which compiles to a single .wasm file. I can add nuget references to SkiaSharp and the SkiaSharp.NativeAssets,WebAssembly and it appears to compile file. But when I try to call Skia methods from my code, I get a DllNotFoundException for libSkiaSharp.
"System.TypeInitializationException: TypeInitialization_Type, SkiaSharp.SKImageInfo --- System.DllNotFoundException: libSkiaSharp at SkiaSharp.SKImageInfo..cctor()
SkiaSharp is supported in Blazor Wasm so I assumed it would work in Wasi Wasm. Is there some extra build step I need to add to get the native assets statically linked into my wasm file?
Beta Was this translation helpful? Give feedback.
All reactions