H
Howard Swope
At runtime I search a directory for assemblies and load them into the
application domain. I use a PropertyGrid to set properties on objects in
these loaded assemblies. The PropertyGrid can enumerate the properties
without any problem, but will not use TypeConverters that are specified and
located in the dynamically loaded assemblies. If I add a reference to the
dynamically loaded assembly in the assembly that uses the PropertyGrid, the
TypeConverter will be used.
I don't quite understand what is going on here. Obviously the PropertyGrid's
assembly can find the type information from the dynamically loaded
assemblies, because it populates the grid. Why won't it use the TypeConverts
to implement the expandable property functionality? As I mentioned if I add
a reference to the assembly that uses PropertyGrid everything works, but
usually I will not have these assemblies at build time.
Any thoughts?
application domain. I use a PropertyGrid to set properties on objects in
these loaded assemblies. The PropertyGrid can enumerate the properties
without any problem, but will not use TypeConverters that are specified and
located in the dynamically loaded assemblies. If I add a reference to the
dynamically loaded assembly in the assembly that uses the PropertyGrid, the
TypeConverter will be used.
I don't quite understand what is going on here. Obviously the PropertyGrid's
assembly can find the type information from the dynamically loaded
assemblies, because it populates the grid. Why won't it use the TypeConverts
to implement the expandable property functionality? As I mentioned if I add
a reference to the assembly that uses PropertyGrid everything works, but
usually I will not have these assemblies at build time.
Any thoughts?