Tewr
Hello! No! For a clickable element, an input is always necessary. The native file chooser dialog only appears from clicking on an input type=file. Either as a hidden underlying, or...
If I would do this, I would create a div as in the first example. Once that works, add two inputs, as in the second example. Manage a common stream...
Hello. Thank you for your feedback. No plans for shared worker api. It could be interesting I guess, but probably quite a different api compared to the one already implemented...
This part should also profit from a build-time created list of assembly-dll maps, to avoid problems like the ones in #64
Maybe, but far from simple. The serialization of the expression depends on the default expression serializer: https://github.com/Tewr/BlazorWorker/blob/master/src/BlazorWorker.WorkerBackgroundService/SerializeLinqExpressionSerializer.cs There is no simple way of replacing this serializer with you own implementation,...
@bpyzik Do you mean IFileListEntry ? https://github.com/SteveSandersonMS/BlazorInputFile/blob/master/BlazorInputFile/IFileListEntry.cs That interface has a stream reference. Streams are, by their nature, not serializable. There is [an issue](https://github.com/Tewr/BlazorWorker/issues/3) open for supporting streams though.
This issue is for supporting Streams in the service contract (either as an argument or as a return type). Just using a stream inside the worker should work just fine,...
Mentioned in https://github.com/dotnet/aspnetcore/issues/17730#issuecomment-879407934_ but as a full process kill, which is not really neccessary unless you would want to unload any dynamically generated dlls
Hello. Blazorworker works primarily with Blazor ( as opposed to React/Angular/Vue/jQuery/whatever) and all examples in the demo apps. That said, you're not the first person who had this idea, and...
Hello. I have not looked into that but I'd not expect it it to work out of the box in any trivial way. That said, I have skimmed over a...