.NET Framework Bookmark and Share   
 index > 64-Bit .NET Framework Development > Need help on communicating to out-of proc COM Server
 

Need help on communicating to out-of proc COM Server

Hi All,

I have a out-of proc COM server (32-bit executable) and two proxy dlls (32-bit as well as 64-bit). I want to communicate with the COM server through a C#.Net application. The easiest way possible is to get the Wrapper of COM server from its tlb file (thru tlbimp.exe) and use it in any C#.Net application but i want to go through the proxy dlls. Please let me know, if anyone has useful information aout how to communicate to out-of Proc COM server through proxy dlls........

Thanks in advance Smile

NaveenP
I think DCOM should be what you really need in this case.

Actually, you don't need to write two proxy DLLs, since your component is a out-of-proc and will not run with the consumer of your component in a same memory space. So the bitness of your application and the consumer can be different.

For remote consumer of your process, you need more actions to make it work. For more details, please visit How to create COM object in remote machine (DCOM server).


Feng Chen
I'm not sure about what exactly you mean by the "two proxy dlls" and the reason you have to use it, could you please clarify? How exactly you're creating them?

And is your .net application 32bit or 64bit or just compiled as "Any CPU"?
Feng Chen

Hi Feng,

Actually i mentioned two proxy dlls, just to make things more clearer.......As i have mentioned that the out-of proc COM server is a 32-bit executableso to make any application (either of 32-bit or 64-bit) communicate with 32-bit out-of proc COM server, i have provided two proxy dlls one is in 32-bit format and another is in 64-bit format. so if any 32-bit application wants to communicate with out-of proc server, he will go thru 32-bit proxy dlls and if any 64-bit app wants to communicate with out-of proc COM server thenit will go thru 64-bit proxy dll.

My .Net appl is in 32-bit format.

I need any help on how to communicate to out-of proc server in C#.Net. specially if the out-of proc COM server is running on some other machine. Above mentioned lines are completly my assumption as i m not sure if the only way to communicate to a out-of proc COM server is thru proxy Dlls..

NaveenP
I think DCOM should be what you really need in this case.

Actually, you don't need to write two proxy DLLs, since your component is a out-of-proc and will not run with the consumer of your component in a same memory space. So the bitness of your application and the consumer can be different.

For remote consumer of your process, you need more actions to make it work. For more details, please visit How to create COM object in remote machine (DCOM server).


Feng Chen

You can use google to search for other answers

Custom Search

More Threads

• 64 bit rookie question
• J# and x62
• debug error
• mscoree.dll 64 bit
• Can a managed code application run in native 64-bit and access shared memory with a 32-bit app running in WoW64?
• iis 6 64 bits more slower than iis 6 32 bits, what happens?
• How to create a new event source in event viewer?
• DAQ - 32 bit ODBC DSN access in vs2005
• Trouble with a .net 2/3.5 app developed for x86 when running on an x64 platform.
• Attempted to load a 64-bit assembly on a 32-bit platform while refering Sharepoint.dll