04-18-2018 03:53 AM
@aRCo wrote:
wiebe@CARYA a écrit :
@aRCo wrote:
Which other solutions could I have implemented?
A dll.
Yes, thanks! I'll try to find the time to implement this other solution 😉 Have a nice day
I think you'll find it will dissolve the entire problem. That is why I mentioned it earlier .
04-18-2018 03:58 AM
BTW. Other solutions are for instance memory mapped files, named pipes, even TCP\IP. But those solutions are used for communication between two running processes. Since you want to call and collect the result, it's more like a function you're invoking. That's why a dll would fit, that's exactly what a dll is for.
Still two choices: a "normal" dll, or a .NET assembly. When I have to use a dll, I prefer .NET. When building one, a normal dll might be easier. Both are good options.