AFAIK, COM Interop under CF 2.0 only works with in-proc servers.

Signature
Neil Cowburn
Principal Partner
OpenNETCF Consulting, LLC.
Managed Code in the Embedded World
http://www.opennetcf.com/
http://www.smartdeviceframework.com/
Sorry,
but I do not agree with you. WE SUCCEEDED in making CF2.0 work with
out-of-process COM server using a proxy/stub DLL that implements the CUSTOM
mashaling.
The only think we noticed is:
- foreach directive fails because IComEnumerator cannot be marshaled;
- for some reason, if I put a breakpoint in a event handler and this
breakpoit is hit, Visual Studio crashes. If I remove the breakpoit the
application works great. Inside the event handler we of course cannot reach
any graphical object but we can use Invoke.
Can you explain me these behavior?
Kind regards,
Andrea
> AFAIK, COM Interop under CF 2.0 only works with in-proc servers.
>
[quoted text clipped - 14 lines]
> > Kind regards,
> > Andrea
Neil Cowburn - 30 Mar 2007 16:37 GMT
I would class that as not working. If you need to implement a custom
marshaller in native code, then out-of-proc COM *clearly* isn't working
directly from CF 2.0.

Signature
Neil Cowburn
Principal Partner
OpenNETCF Consulting, LLC.
Managed Code in the Embedded World
http://www.opennetcf.com/
http://www.smartdeviceframework.com/
> Sorry,
> but I do not agree with you. WE SUCCEEDED in making CF2.0 work with
[quoted text clipped - 31 lines]
>> > Kind regards,
>> > Andrea
Andrea - 30 Mar 2007 18:00 GMT
Just in case we run into problem:
- is it possible to make an in-proc COM server that exports the same
interface(even event, inbound interface) as the COM.EXE server and use it in
order to overcome the CF2.0 limitation?
- are there any workarounds to do in order to make our out-of-process COM
server running?
Kind regards,
Andrea
> I would class that as not working. If you need to implement a custom
> marshaller in native code, then out-of-proc COM *clearly* isn't working
[quoted text clipped - 35 lines]
> >> > Kind regards,
> >> > Andrea