Out-of-Process DLL
-
Dear COM programmers, I hope somebody can give me some thoughts about a problem I have. I am a complete newbie at COM programming and desperately trying to write a DLL library for a simulation program I am using. The simulation program allows me to write a DLL library with user defined functions. Now my plan is to write a general DLL library, which calls MATLAB to do the actual work. I am already using the MATLAB engine to let my DLL(simulation program) call user defined functions in MATLAB. But, I also need MATLAB to call functions in my DLL, from within the user defined functions written in MATLAB. For this I wanted to setup an out-of-process server within my DLL library. I succeeded at writing an out-of-process server in a normal EXE application and I could let MATLAB call functions and transfer data to my EXE application. But my real question is how to write an out-of-process server in a DLL? Is it at all possible, because usually DLL’s are in-process-servers? Kind regards, Marcel Dijkstra
-
Dear COM programmers, I hope somebody can give me some thoughts about a problem I have. I am a complete newbie at COM programming and desperately trying to write a DLL library for a simulation program I am using. The simulation program allows me to write a DLL library with user defined functions. Now my plan is to write a general DLL library, which calls MATLAB to do the actual work. I am already using the MATLAB engine to let my DLL(simulation program) call user defined functions in MATLAB. But, I also need MATLAB to call functions in my DLL, from within the user defined functions written in MATLAB. For this I wanted to setup an out-of-process server within my DLL library. I succeeded at writing an out-of-process server in a normal EXE application and I could let MATLAB call functions and transfer data to my EXE application. But my real question is how to write an out-of-process server in a DLL? Is it at all possible, because usually DLL’s are in-process-servers? Kind regards, Marcel Dijkstra
Hi I think there was the option to write a COM-DLL and instead of load it into the client, you have the option to configure it just to be loaded as a surrogate, in a system proccess. Have a look in the COM section, in COM Architecture. One of these articles explain how to configure the registry (i'm not sure about this, just trying to remember). Regards.
-
Hi I think there was the option to write a COM-DLL and instead of load it into the client, you have the option to configure it just to be loaded as a surrogate, in a system proccess. Have a look in the COM section, in COM Architecture. One of these articles explain how to configure the registry (i'm not sure about this, just trying to remember). Regards.
Hi Gizzo, DLL surrogate is the thing I was looking for. I looked at the COM Architecture section and found articles on MSDN. I think this will keep me busy for some time. Thanks, Marcel