<div>
<div class="content wysiwyg-content">
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??
</div>
</div>


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??

COM Marshaling

Most development for the Microsoft platform is done utilizing the technologies supported by the.NET framework. Other development is done using Visual Basic for Applications (VBA) for programs like Access, Excel, Word and Outlook, with PowerShell for scripting, or with SQL for large databases.

Microsoft Development

Kernel and system programming is the process of creating the software necessary for a computer or device to function and operate other programs. Some operating systems (such as Microsoft Windows) are proprietary, but others, such as the various Linux distributions, are open source.