You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The examples have Module.FromTextFile and such, and I have a .wasm file (binary) I tested with wasmtime and works, but using wasmtime-dotnet I and Module.FromFile I get:
Unhandled exception. Wasmtime.WasmtimeException: WebAssembly module 'WasmFile' is not valid: failed to parse WebAssembly module
Caused by:
expected a WebAssembly module but was given a WebAssembly component
at Wasmtime.Module.FromBytes(Engine engine, String name, ReadOnlySpan`1 bytes)
at Wasmtime.Module.FromFile(Engine engine, String path)
I built the .wasm with componentize-dotnet. It looks like component support seems to be just coming up in the c-api, so we could take advantage of things like wasmtime_component_new, wasmtime_component_instance_get_func, wasmtime_component_func_call, wasmtime_component_linker_new, etc.
Since it seems like it's a new Linker, would you bundle it with the existing Linker and add a mode switch? Or make a whole new ComponentLinker for example?
The component model isn't supported here yet, there is a tracking issue in #324 and first pass here: #346. Take a look, any feedback you have on the suggested approaches is welcome!
Activity
jsturtevant commentedon Aug 20, 2025
The component model isn't supported here yet, there is a tracking issue in #324 and first pass here: #346. Take a look, any feedback you have on the suggested approaches is welcome!
Going to close this issue in favor of #324