[Mono-devel-list] Creating types at runtime

Cinq - Eduardo Vellasques e.vellasques at cinq.com.br
Wed Mar 10 06:39:38 EST 2004

It also interests me a lot, and I also would like to contribute to it.
What you mean August, is to implement the Mono version of the .NET
System.Runtime.InteropServices Namespace Classes. They make possible the use
of COM unmanaged classes for .NET managed application.
If it is not already implemented, I would like to contribute too.


Eduardo Vellasques
HSBC: 340-5496
Cel.: 9144-8306

--------- Mensagem Original --------
De: August Steinbacher <august.steinbacher at gmx.net>
Para: Mono Development List <mono-devel-list at lists.ximian.com>
Assunto: Re: [Mono-devel-list] Creating types at runtime
Data: 10/03/04 08:08

> Thanks Jon...
> to be more precise, the goal of my work is to dynamically (at runtime)
> integrate type information into the Mono runtime and thus allow Mono
> programs to use externally defined types as if they were available in the
> managed environment. The external types could come from C / C++
> applications, and they must have a well-formed type-description given as
> XSD-schema, which resides somewhere in a kind of metadata.
> At the moment, everything is quite fuzzy for me, so I'm happy about every
> kind of help. So, thank you for your answer, now i know where to start. I
> hope I'm getting more into Mono the next days and can contribute to the
> Mono-project in the future...
> best regards,
> august
> &gt; Below...
> &gt;
> &gt; On Tue, 2004-03-09 at 08:31, August Steinbacher wrote:
> &gt; &gt; Hello all,
> &gt; &gt;
> &gt; &gt; I am starting to work on a mechanism that allows managed
programs to use
> &gt; &gt; unmanaged objects and vice versa.
> &gt;
> &gt; Sounds like Platform Invoke, depending on how you define
> &gt; objects.&quot;  Unmanaged C++ objects?  Or &quot;object&quot; meaning
> &gt; Something else?
> &gt;
> &gt; &gt; My first task is to create a type object at runtime from a given
> &gt; &gt; description in the form of XSD.
> &gt;
> &gt; Simple enough -- you want to write a compiler that translates the XSD
> &gt; into a set of types.  Look into System.Reflection.Emit.  Looking at
> &gt; source to &quot;mcs&quot; might be helpful as well.
> &gt;
> &gt; &gt; So my question is if anybody has concerned with this topic and
> could
> &gt; &gt; give me a slight kickoff and head me in the right direction
(since I'm a
> &gt; &gt; bloody mono-newbie...) ?
> &gt;
> &gt; My &quot;slight kickoff&quot; is above, though you haven't provided
> &gt; information about what *exactly* you're trying to do.
> &gt;
> &gt; One thing to keep in mind is that Mono is a statically-typed
> &gt; environment.  Which means that you can't have existing, pre-compiled
> &gt; code directly reference a set of classes you'll be generating at
> &gt; run-time, as the classes won't exist yet. :-)
> &gt;
> &gt; A workaround would be to define a set of interfaces/base classes that
> &gt; your generated code will implement/derive from, and that existing
> &gt; can compile against.  Regardless, your design will need to take this
> &gt; into consideration.
> &gt;
> &gt;  - Jon
> &gt;
> &gt;
> &gt; _______________________________________________
> &gt; Mono-devel-list mailing list
> &gt; Mono-devel-list at lists.ximian.com
> &gt; http://lists.ximian.com/mailman/listinfo/mono-devel-list
> &gt;
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

Cinq Technologies - http://www.cinq.com.br

More information about the Mono-devel-list mailing list