Actually, if you look more carefully you'll see that Steve's right -
System.ComponentModel *does* provide a set of facilities that do provide
very similar services to those available through reflection. (They are
a subset - reflection is more powerful. But it's simply not accurate to
say that "Sy
System.ComponentModel is not related, at all, to Reflection. You cannot use
its methods to do the things that Reflection does. ComponentModel is (quoting
from URL below) "to implement the run-time and design-time behavior of
components and controls." It's not for finding out about (and possib
Since discovering the power of reflection in .NET, I've been able to realize
significant benefits.
My helper class for Reflection contains methods that use Assemblies,
System.Type, EventInfo, PropertyInfo, etc. Most of these types are located
in the System.Reflection namespace.
Everything works f
