Dynamically creating a type at runtime.

[=?Utf-8?B?UHN5cGhlcjg=?=]

I really, really want to store some settings somewhere that my control
utilizes to create new object(s)(i.e., class, struct) at runtime without it
knowing about the type it could create at compile time. The type would
support a particular interface or base class let's say.

Couple thoughts:

1. Store the 'serialized' data in the store and let the deserializer create
it for me.
Slower
2. Lookup table (but then my control needs to know all the types it could
create before compile time).
Would be faster than the serialized version.
3. ActiveX control
Here we would have the coclass lookup issue.
4. ?

There must be an easier way. How does the serializer instance the type from
data? I know it stores the class name in the stream but how does it go from
just the classname to the object instance?

Thx for the help.

[Ignacio Machin ( .NET/ C# MVP )]

On Apr 17, 12:24*am, Psypher8 <Psyph...@discu ssions.microsof t.com>
wrote:

I really, really want to store some settings somewhere that my control
utilizes to create new object(s)(i.e., class, struct) at runtime without it
knowing about the type it could create at compile time. *The type would
support a particular interface or base class let's say.

Couple thoughts:

1. *Store the 'serialized' data in the store and let the deserializer create
it for me.
* * Slower
2. *Lookup table (but then my control needs to know all the types it could
create before compile time).
* * *Would be faster than the serialized version.
3. *ActiveX control
* * Here we would have the coclass lookup issue.
4. *?

There must be an easier way. *How does the serializer instance the type from
data? *I know it stores the class name in the stream but how does it go from
just the classname to the object instance?

Thx for the help.

Hi,

You need to provide more details, but you can always use an Object
reference and access all the members by reflection.
Another alternative that I eager you to explore is define an interface
and make that "dynamic" object you have implement it, in this case at
runtime you can use any type of object as long as it implements that
interface

[=?Utf-8?B?UHN5cGhlcjg=?=]

Here's an example:

At runtime I load a string that identifies a type.
Example: "SomePackage.So meFolder.SomeTy peObject"

I would like to create that type now.

I have tried utilizing the Assembly object but it only exposes types inside
that assembly which is nice but won't work in the case I'm developing.

[Marc Gravell]

Does Activator.Creat eInstance come close? Note that you might need to
work the assembly-qualified names to get the best results.

Marc