Your question is very similar to this one: WebAssembly only supports i32 / i64 / f32 / f64 value types as well as i8 / i16 for storage. This means that you can’t pass in pointers. What you’re doing is totally sane when you’re coming from a C++ point of view (no need to apologize … Read more
Creator of Blazor Steve Sanderson used JavaScript interop for similar task during one of his last presentations. You can find example on BlazorExcelSpreadsheet Solution includes three parts: 1) JavaScript function saveAsFile(filename, bytesBase64) { var link = document.createElement(‘a’); link.download = filename; link.href = “https://stackoverflow.com/questions/52683706/data:application/octet-stream;base64,” + bytesBase64; document.body.appendChild(link); // Needed for Firefox link.click(); document.body.removeChild(link); } 2) C# … Read more
WebAssembly only supports a few numeric types, which is all that can be returned via an exported function. When you compile to WebAssembly, your string will be held in the module’s linear memory. In order to read this string from the hosting JavaScript, you need to return a reference to its location in memory, and … Read more
WebAssembly doesn’t natively support a string type, it rather supports i32 / i64 / f32 / f64 value types as well as i8 / i16 for storage. You can interact with a WebAssembly instance using: exports, where from JavaScript you call into WebAssembly, and WebAssembly returns a single value type. imports where WebAssembly calls into … Read more