Smokey Grindle wrote:
Well we know for certain we have to create objects on the fly based off of a
type name specified in a database row... so right now we have the object
type... just need to create the object
Ah ha!
That's one of the Good Reasons for doing this.
As Tom said, Type.GetType and Activator.CreateInstance.
This will work well for Framework-defined Types but watch out when you
start trying to use Types defined in /your own/ assemblies - whatever
process is doing all this has to be able to "get hold of" (i.e. Load)
the defining Assemblies. Can make for some fun deployment issues.
HTH,
Phill W.