How to run an 32bit SDK inside a 64bit program?

You cannot directly use use a 32-bit assembly in a 64-bit process.

If possible, obtain or create a 64-bit version of the desired assembly.

If a 64-bit version of the assembly cannot be obtained or created you could create a 32-bit WPF application that is capable of using the assembly. Presumably, this is an undesirable alternative.

In general, you could use a 32-bit process that consumes the 32-bit assembly as an intermediary. The 64-bit process starts the intermediary and uses inter-process communication to instruct it to execute the assembly's methods and return the results.

Hi @RLWA32

I was considering using a Windows Service as an intermediary since I have experience creating services. However, I am also open to exploring other options. Currently, I'm in the process of setting up a Named Pipe for inter-process communication, but I've also read about gRPC, which I haven't used before. Is there a significant difference between the two, and can you explain when it would be preferable to use one over the other?

@Xavier Julies Sorry to disappoint, but I don't have any experience with gRPC. A Windows Service is probably not what you want. Administrator privileges are required to install and control services so that creates a limitation. And, services typically run in non-interactive session 0 while your application is running in a different interactive session so that adds an additional bit of complexity. I suggest using an intermediary process that the WPF application can start that runs in the same session and in the same security context.

Hi @RLWA32 ,

You're right about the Windows Service. A "consoleless" console application that operates without a traditional console interface should still be effective for inter-process communication, correct?