ianm at ActiveState.com
Sat Mar 29 22:10:47 EST 2003
Jonathan Pryor wrote:
> What time-frame are you looking for? :-)
> XPCOM is, for most intents and purposes, Microsoft COM (with "ns"
> prefixed to the interface names, and some names changed; for example,
> IUnknown --> nsISupports, but they have the same methods & semantics).
thats true in terms of design and in fact even guid values - nsISupports
and IUnknown use the same guid. However they have diverged quite some
way in terms of implementation. You can't load a COM component using
the xpcom infrastucture for example.
> If Mono isn't a requirement for you, you could probably write XPCOM
> components in C# under .NET. That would probably be a good idea,
> anyway, just to get an idea of the complexities involved.
I don't think it wuld be any easier to build under .NET. You would have
to essentially re-write the COM interop layers for XPCOM. At one stage
you could build xpcom components in java - I'm not sure if that is still
true, so implementing a binding is certainly possible.
> - Jon
> On Sat, 2003-03-29 at 11:19, Jose Luis Sampayo wrote:
>>Hallo. First of all, I´m sorry if this messages appears more than once
>>in the list, I think I sent it first from a wrong mail account.
>>And now the real content:
>>Maybe this is a stupid question, but anyway...
>>After reading a bit (too bit) about Mozilla´s XUL, XBL, XPCOM... a
>>question arises for me:
>>would it be possible to code an XPCOM component in C#...?
>>I mean, creating a mono -.net component - .dll that worked as a XPCOM
>>component. This way we could code UIs with Mozilla-XUL and combine it
>>with a behaviour written in mono-.net.
>>Thanks for your time.
>>Jose Luis Sampayo
>>Mono-devel-list mailing list
>>Mono-devel-list at lists.ximian.com
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list