You are on the right track.  Reflection is a set of classes that allow you
to examine the details of those classes.  You can obtain all the information
about properties, methods etc.  There are also methods which allow you to
create an object using reflection and call the methods of the object without
having compiled code to access the object (actually there is compiled code
but that code is the reflection code not the object code).

It can be used to dynamically load assemblies for things like application
plug-ins.

To illustrate what reflection can do, I created a navigator control which
shows the contents of a SQL Server.  It uses the classes from SMO and
reflection.  There is only one entry which is required for SMO to work and
that is a connection.  After that I use reflection to enumerate the
properties such that I can determine collections etc.

Hope this helps
Lloyd Sheen

I think this can be understood well, just like all the programming
concepts, only by practice,
especially on some meaningful project.

I could tell you I could not live without reflection ! :-)))

Anyway, to start with here is an excercise which will make you
understand it better.

Homework   :-)
===========

Take o write a program where you have a serializable class with a
some
<non serialized> fields and some "reference" type fields (not only
value type fields).

Create a dialog form to allow an user editing the field and the
properties of an instance of this class
with a "CANCEL" feature. In other words, if the user "cancels" the
dialog, the object must be
"restored" completely and perfectly to its original state [careful
with non serialized reference values].

Post here your solution for discussion and grade   :-))

Tommaso

Reflection means that the code can reflect about itself. Code can examine
and get information about itself. This is possible by additionally having
meta data in the assemblies that describes the code
(classes/types/methods/parameters...).

Armin