Using standard coding techniques, you are pretty much lost. In .NET, however,
you do have a very real option using Reflection and code generation.
Reflection.Emit is what you want to examine. It allows you to take code
created on the fly and compile in memory and use in your process. If the
dynamic classes are called again, you do have the option of saving off the
code. Not the easiest to implement, but flexibility is always a bit more time
consuming.

---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

There are some publications that could be helpful for you:

Yoder J.W.; Johnson, R.: The adaptive object-model architectural style.
http://www.adaptiveobjectmodel.com/WICSA3/ArchitectureOfAOMsWICSA3.htm

Riehle, D.; Tilman, M.; Johnson, R.: Dynamic Object Model. PLoP 2000

At least you should have a look at http://www.adaptiveobjectmodel.com/

Daniel

Demetri,

What you want is in my opinion late binding. You can do that using Option
Strict Of in VBNet or reflection in another program language. However keep
in mind that both will decrease your performance.

Cor

   Define what you mean by "Properties"..

   What you describe differs in many respects from "Properties" as defined
in C#. Before we can give you any meaningful answer, we need to know what
features of C# properties are needed in these "Properties".   (Notably, we'd
need to know how & where you plan as access these properties)