How do you use SDK for signing on clients` desktop ?

Hi all,
I have a desktop application with a language that does not support .Net Dlls (VB6) . So , I am not able to use SDK Dlls for signing in my project . Instead , I use CLI commands and call cmd from my application .

I can use both “Fatoora” and “FatooraNet” commands in CLI .

As you may know , these commands and associated EXEs (jq for java and FatooraNet.exe for .NET) are designed to read Certificate( CSID or PCSID ) and Private Key from a file in a predefined file path .

My question is : How can we sign on the client`s desktop ?

Should I download all the SDK and register it and call CMD as I am doing now ?

Note that : as I mentioned above , CLI whether Java or .Net both depend on PK and CERT as files written on disk . I think this behavior is not too good on the clients side for two reasons :

1 - I must install SDK on client PC ( 450 MBs are too much I think ) or (essential files only ) . A side problem is how even can I determine which ones are essential and which ones are not ? .

2 - Not secure because every time I need to sign I must write PK and CERT to these two files on disk .

I know that .Net users are directly using .Net DLLs but this cant be done on my programming language . I asked for someone to wrap the SDK DLLs in an EXE and I call it from my application . It was working fine until the last update of SDK and I cant reach the programmer right now and I also dont want to depend on an exe that is made by a language I can`t handle until I am aware of .NET languages .

So , I want to directly use EXEs that are shipped with SDK . whether Jq.exe for java or FatooraNet.exe in .NET

So , any ideas to solve this issue ?

Morning @Helox

Thanks for reaching out, welcome to our community.

You mentioned that the SDK was working fine until the last update, what is the exact issue that you are facing?

Thanks,
Ibrahem Daoud.