newbie question about how to make this program client/server

[t***@intex.com]

I have a VB compiled executable that makes calls directly to a C DLL.
Only BSTR are passed back and forth between these calls.

I would now like to make a version where my DLL runs in a separate
process space (so that it can take advantage of 64 bits while keeping
my VB program in 32 bit land). My VB program would call the same
functions but these functions would be stubs which would call some
other function that could use interprocess communication to talk with
the DLL.

What would be the simplest way of doing this? I've read the MSDN
section on IPC but would love to see more concrete examples of this.

Thanks,

Ted

[Scott McPhillips [MVP]]

Post by t***@intex.com
I have a VB compiled executable that makes calls directly to a C DLL.
Only BSTR are passed back and forth between these calls.
I would now like to make a version where my DLL runs in a separate
process space (so that it can take advantage of 64 bits while keeping
my VB program in 32 bit land). My VB program would call the same
functions but these functions would be stubs which would call some
other function that could use interprocess communication to talk with
the DLL.
What would be the simplest way of doing this? I've read the MSDN
section on IPC but would love to see more concrete examples of this.
Thanks,
Ted

I suggest using a named pipe. The MSDN page for CreateNamedPipe has a link
to pretty good sample code.