Yes, that's his first name, but I'm jumping back on this thread as he is working on another task at the moment.
The TelerikUpload component does something slightly different - it sends the files to an endpoint on a server (might not even be the same server that hosts the blazor app, might not even be your server at all). It does not give you the file stream in the Blazor app. We decided to do that async upload to an endpoint for two reasons: 1) it was what was requested more often and 2) it's the one that's harder to do (requires quite a bit more JS Interop).
So, if this will serve you (e.g., you can add a controller in your app to handle the upload from client to server, and then save it to the vault), it can be the right tool for the job.
To get the memory stream (or any stream, or a byte) into your Blazor app code, you need a FileSelect type of component which typically does not upload the file but just gives you an event with the stream/array. We don't have one as part of our component suite (you can post a feature request on our portal if you want to see one implemented), but you can find an example of making it in our demos - we use it on our Document Processing demos - at the moment it is ~/Shared/FileUpload.razor (it also has some JS Interop, so take a peek at the _Hosts.cshtml) and with our next release it will be called DemoFileSelector.razor to avoid confusion with a built-in component in the suite, but the code will be the same.
Progress is here for your business, like always. Read more
about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.