tags:

views:

34

answers:

1

I know I read all about surrogate process, and I was able to create a surrogate COM but it either all works in 32bit or all works in 64bit.

What would be the correct structure?

1) 32.dll <- 64.com <- 64.exe 2) 32.dll <- 32.com <- 64.exe

I tried both of the above but I did not succeed to call the 32.dll?

A: 

This is defenetly what you want: 32.dll <- 32.com <- 64.exe If it does not work, show more details HOW it does not work.

Also, if you are not doing much calls, you may communicate via sockets (just a backup plan).

BarsMonster
actually I am only calling one function passing a filename but the dll has to be hosted by an application domain because it creates a window and wait for a user response.
Canan Erdol
what did you mean by socket calls. For example, create a com that listens to a port and when connected fire up the 32.dll? Maybe I could to that with a service?
Canan Erdol
The actuall problem with 32.dll <- 32.com <- 64.exe is that when I create the com object in the 64.exe it can not find it because it is registered as 32.com, somehow the WOW divert it as an error: unregistsred class.
Canan Erdol
Yes, 32bit app listens a port, and executes commands from it. You send commands from 64bit app. This will work at all times :-)
BarsMonster