filestream | dotnet core web api - optimising file upload

It is because of the node-fetch package. As recent versions of this package only support ESM, you have to downgrade it to an older version node-fetch@2.6.1 or lower.

npm i node-fetch@2.6.1

This should solve the issue.

Use Promise.all to await the resolution of all promises that are created in the for-await loop:

I may have found a solution using the links from @AlwaysLearning. The first sub actually answers my question to upload a file to a remote FILESTREAM SQL Server. The second sub downloads all uploaded files into a given directory.

As alluded to in the comment from @Daniel A. White, you are doing a risky thing -- trying to write to a file, in a handler that's provided on an "if all else fails" basis. Some examples:

• if the disk is full and the File Logger can't write (File sinks dont necessarily do that, but if they wanted to communicate failure, it would be via the SelfLog)
• if a message string is malformed (Serilog logging calls will never throw; this is based on a fundamental tenet in the wiki about the logging not being important enough to stop a working app from working)

While the Serilog debugging and diagnostics Wiki page currently shows an example of writing to a file, that's simply not the nature of the contract -- it must not fail.

Hence, if you actually want to emit the SelfLog to a file, you will need to add a try/catch and swallow the exception in the handler.

I would say its pretty questionable value to have a file as a backup when the File Sink is your primary output. This is doubly the case as you don't have any mechanism to ensure it gets trimmed (imagine you had a tight loop logging with a malformed message string - it would fill your disk eventually).

I personally have handled this tradeoff by echoing the SelfLog to my Console Sink (which logging won't throw, per the above) on the basis that the operating environment (think Kubernetes) can be trusted to capture it, or alert.

FileStream defaults to only allowing read sharing which is not compatible with how you've opened your c++ file. You need to request write sharing too:

But the downloaded file in browser does not open correctly

That is probably because you

1. First create a Word document
2. And then download var randomBinaryData = new byte[50 * 1024];

the downloaded file in browser

Check those. Are they exactly 50 * 1024 bytes ?

--

Also, you shouldn't pass the full C:\... path to the download funtion.

This answer explains how, in Elmish.WPF, progress updates to the user interface can be done from an async.

I have created an example on GitHub that demoes this. The example also demoes another way to call async functions and receive results. And it also demoes how to use mkProgram instead of mkSimple. The demo can be used as a starting template for your Elmish.WPF applications.

This snippet from the demo show the essential code involved in updating a user interface from an async.

Both techniques are based on code from the Elmish Book. You will find a lot of code there that is useful also in Elmish.WPF.

I haven't tried to update a progress bar here, only a status text box, but from this you'll very easily figure out what to do to update anything.

There was a breaking change to the way DeflateStream operates in .NET 6. You can read more about it and the recommended actions in this Microsoft documentation.

Basically, you need to wrap the .Read operation and check the length read versus the expected length because the operation may now return before reading the full length. Your code might look like this (based on the example in the documentation):

In ASP.NET Core Web API, it binds application/json format data by default. But what your model need is multipart/form-data type data. So you need [FromForm] attribute to specific the source.

I use Swashbuckle.AspNetCore version 5.6.3 in ASP.NET Core 3.1: