[Mono-dev] RE: Com Interop Patch

Jonathan S. Chambers Jonathan.Chambers at ansys.com
Sat Jan 7 09:00:52 EST 2006

     I have no clue. I have never used Wine. I believe that Wine uses a binary compatible implementation of COM. If so, in my ignorance I don't see why it would not be possible. It may need some additional setup, there may be threading issues, etc. I'll try it out when I have free time; or you can. As long as the mono runtime can find ole32 (and maybe oleaut32) I think you should be ok. If Wine needs intialized you may need to pinvoke that routine before doing any COM stuff.

- Jonathan

-----Original Message-----
From:	Alexandre Miguel Pedro Gomes [mailto:alexmipego at gmail.com]
Sent:	Sat 1/7/2006 8:53 AM
To:	Jonathan S. Chambers
Cc:	mono-devel-list at lists.ximian.com
Subject:	Re: [Mono-dev] RE: Com Interop Patch

Would it be possible to use COM in Linux, using Wine for instance?

On 1/6/06, Jonathan S. Chambers <Jonathan.Chambers at ansys.com> wrote:
> The patch was too big. Attached is the patch to mono. The next email
> will have the patch to mcs.
> -----Original Message-----
> From: Jonathan S. Chambers
> Sent: Friday, January 06, 2006 11:33 AM
> To: mono-devel-list at lists.ximian.com
> Subject: Com Interop Patch
>         Here's a first attempt at a patch for COM Interop. This only
> provides support for RCWs (Runtime Callable Wrappers), i.e. using
> unmanaged COM components from managed code. This should support both
> classes used from Interop Assemblies (where metadata is known), as well
> as bare interface pointers (with no metadata) who are wrapped using
> __ComObject.
>         The patch doesn't seem to introduce any regression failures, and
> theoretically no code in this patch should even be hit unless you are
> using COM Interop functionality.
>         Just as a quick update, as much functionality as possible has
> been moved to managed code (either in the Marshal or COMInteropHelpers
> classes). This helps maintenance, doesn't bloat the runtime with
> component specific code, removes compile time dependencies, etc. I'm
> hoping for all code in the runtime to be generic component support code.
> All specific component code (COM, XPCOM, Mainwin COM) will be in
> managed.
>         There's lots left to do, but this provides basic functionality.
> I'm sure the patch needs cleanup before commit, so please let me know
> what needs changed.
> Thanks,
> Jonathan
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

Alexandre Gomes, Portugal

More information about the Mono-devel-list mailing list