FileAPI | FileAPI — a set of javascript tools

Okay, so after digging deeper into the debugger output I managed to figure out the issue. The problem was with using the @Multipart annotation with a GET request, which does not expect a request body. In order to fix this I replaced the two @Part arguments to my request with @Query elements, which is likely better practise anyway.

I am unsure why this throws an exception but doesn't provide any logging output.

here, you need to set mime type of file . Here, I have mention application/pdf instead of ".pdf"

The Windows API is designed to be called from C. Write

I do not know what file_read is, but the compiler tells you that:

• you should not try to cast it to PIMAGE_DOS_HEADER;
• WriteFile needs a pointer as a second parameter: WriteFile( PEFile, &file_read,....

[Edit - new information added to the question]

file_read is the result of ReadFile which is a BOOL (success or failure). Most likely you do not want to write this, anyhow: the third parameter must be the size of the data you are trying to write: WriteFile(PEfile, &file_read, sizeof(file_read), &returned_bytes, NULL);

This will fix your compiling problem but it won’t fix the logic. And we cannot help you since it is not clear what you are trying to do. Maybe WriteFile(PEfile, file_buffer, file_size, &returned_bytes, NULL);?

As recommended by @dlam, I used a switchMap.

Create an instance of the type and pass it by reference. It is equivalent to declaring a local variable in C and passing its address, e.g. DWORD flags; and passing as &flags to be an output parameter.

It also help ctypes error checking by declaring the .argtypes and .restype of the function call, which is similar to declaring a C prototype. ctypes.wintypes has many pre-defined types for Windows.

I've also added an .errcheck attribute that automatically checks the return value and raises Windows exception based on the GetLastError() code, and an enumeration to process the flags into a readable format:

I tried the code, the code returns the same result as you mentioned. The document of FindFirstFileW mentions this API could be used in UWP apps but it will still be limited by the UWP apps as the UWP are running in the sandbox.

If you are trying to find a file and its handle, there is another way that you could do that. You could get a brokered file HANDLE from a StorageFile with the IStorageItemHandleAccess interface or from a StorageFolder with the IStorageFolderHandleAccess interface. After you've got the handle, you should be able to use the handle in some win32 APIs to do what you want.

Besides, if you don't mind using the desktop bridge, you could do it in the desktop apps, and then package it together with the UWP app. Use the UWP app to launch the desktop app which calls the win32 APIs to do the work.

Here is the answer of of my question :

create the file with an inheritable handle and pass that handle to the child process. A simple way to do this is to pass it as a command line parameter. We must pass a SECURITY_ATTRIBUTES structure that specifies TRUE for bInheritHandle to CreateFile and also pass TRUE to the bInheritHandles parameter of the call to CreateProcess.

Create File

Ex:

inputStream.CopyTo(stream) copies the stream synchronously. You'll want to either use a StreamContent instead of ByteArrayContent, or copy the stream asynchronously (CopyToAsync).