[Mono-list] Mixing Mono and .NET dlls?

[Jiří Zárevúcký]

2009/2/21 fevans <fevans at harris.com>:
>
> Miguel's blog on Mono.Options, got me wondering (again) about hybrid
> projects.
> http://tirania.org/blog/archive/2009/Feb-21.html
>
> On the technical side, what are the advantages and pitfalls of mixing dlls
> from both stacks. I develop mainly in Visual Studio. Can I include
> Mono.Options.dll  in my .NET project?

As long as it's a purely managed assembly, it should work the same way
everywhere.
Mono.Options is, so there is no problem at all.

> Another Mono widget I'm contemplating is the Webbrowser form. I use the .NET
> webbrowser form, but I'm not happy with its performance. Also, it doesn't
> work on linux.  I would like to try the mono/gluezilla widget.
> Can I simply include Mono.System.Windows.Forms in Visual Studio?

I guess you must not reference the MS winforms assembly, but I never
tried anything Mono-related on Windows. Perhaps it won't work at all.
I'm not sure how the Mono implementation works.

> And then there's the legal question. Is there anything wrong with swapping
> out bits of .NET with Mono?

I'm not a lawyer (and especially not an EULA reader), but I think that
is like asking "is there something wrong with using my own library?".