I have managed COM from an exe process handler in C #, exposing my application object model to automation, everything works fine. I can access it from unmanaged code (e.g. VC ++), and it starts my external server, and each one works through COM using the type library created for my exe server.
When I try to do this from managed code, say, a C # client application, I refer to my exe server, but it loads the server in the process into the client application.
How can I get it from working with managed code and run it in my process outside the process server?
What I'm trying to do is to expose the application object model in COM through my application so that it can be automated using unmanaged code as well as managed code similar to how Microsoft Office. Everything works fine under unmanaged code through COM, but trying to do the same from managed code only creates an instance of my object in the process.
C # Example:
MyApp.Application app = new MyApp.Application();
It just creates an instance of the object, but I want it to start my COM server too. I missed something here, just wondering if anyone has any advice on what to do or where to look.
source
share