Basically, .NET Compact Framework 1.0 doesn't support COM Interop, nor passing .NET delegates to unmanaged code. But both have alternatives. For example, a third party Odessy CFCOM software that adds wrappers to COM interfaces. Below is a MSDN article on this topic: http://msdn2.microsoft.com/en-us/library/aa446494.aspx. The alternatives for the second case could be: 1). create separate EXEs for unmanaged and managed codes and communicate through windows messages (ArcPad client for ArcGIS Server can use this method) 2). if a managed code calls unmanaged DLL and requires asynchronous callback, the follwoing MSDN article provides details: http://msdn2.microsoft.com/en-us/library/aa446485(d=printer).aspx
Basically, .NET Compact Framework 1.0 doesn't support COM Interop, nor passing .NET delegates to unmanaged code. But both have alternatives. For example, a third party Odessy CFCOM software that adds wrappers to COM interfaces. Below is a MSDN article on this topic: http://msdn2.microsoft.com/en-us/library/aa446494.aspx. The alternatives for the second case could be: 1). create separate EXEs for unmanaged and managed codes and communicate through windows messages (ArcPad client for ArcGIS Server can use this method) 2). if a managed code calls unmanaged DLL and requires asynchronous callback, the follwoing MSDN article provides details: http://msdn2.microsoft.com/en-us/library/aa446485(d=printer).aspx
