• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 608
  • Last Modified:

COM Marshaling

My COM Object is an ATL In-Proc DLL server. From the Client App I created the COM object and get the Interface pointer using CoCreateInstance. I then pass this interface pointer to a worker thread by marshaling the pointer using AtlMarshalPtrInproc and unmarshal the interface pointer in the worker thread using AtlUnmarshalPtr. So far It only works OK on Windows NT but not Windows 95 both version A and OSR2. I've not compiled and registered the Proxy-Stub DLL generated by the MIDL compiler. Is it nescessary to use this proxy-stub DLL when you need to marshal the interface pointer and when is it a must to use this DLL??
0
tdao1
Asked:
tdao1
1 Solution
 
Tommy HuiCommented:
This really depends on your interface. If your interface is a dual or automation interface, then the regular automation marshaller should be able to take care of marshalling the interface between apartments. However, this depends on the version of the automation marshaller. You should get the latest DCOM installer for Windows 95 to get the latest COM/OLE objects.

If your interface is a custom interface, then you will need to register the proxy/stub classes no matter which OS you're using. This will guarantee to work because you're using an interface-specific marshaller.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now