As lupus said, I am working in this area right now and cleaning up a patch. However, what I currently have does not support exactly what you are describing. If you run a managed app or host the mono runtime you will be able to expose managed objects to unmanaged code as a COM object.
      However, I currently have no plans of exposing managed objects as COM servers in a standalone manner (i.e. by calling CoCreateInstance). Basically, I consider that a luxury not a requirement since mono can be easily hosted (and it raises a few other questions like which version of mono to use, what library to expose the COM entry points in, registry entries, etc). I do think you could easily host mono and expose your own version of CoCreateInstance to do what you need, if necessary.

Thanks,
Jonathan

On 10/30/06, Paolo Molaro <[EMAIL PROTECTED]> wrote:
On 10/29/06 Goldstein, Nachum (Jonathan) wrote:
> Does anyone have step-by-step instructions on how to build a COM server
> in mono, that can be installed on a Windows machine?

The current mono only supports using COM objects, not exposing managed
code as a COM server, AFAIK. Jonathan Chambers is working on what you
need and he should have a patch ready shortly.

lupus

--
-----------------------------------------------------------------
[EMAIL PROTECTED]                                     debian/rules
[EMAIL PROTECTED]                             Monkeys do it better
_______________________________________________
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list

_______________________________________________
Mono-list maillist  -  Mono-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to