A few notes
* When you load an Assembly and the Type, all this code will stay in your
process memory forever, untill you shut down. Might be worthwhile to do the
extracting in a separate application domain, and just get the bits you want
as strings back into your application.
* When you use LoadFrom, you are changing the way the Fusion Loader works,
and you are changing the context in which they are loaded. So when you're
calling Load from the referenced list you probe, the fusion loader is going
to look inside the path of the host application doing the probing, and might
not be able to find the dlls. Use the Fusion log viewer to see how it is
influenced when probing for referenced assemblies. Eventually, either always
use LoadFrom, or load them in a separate AppDomain by setting the path to
the one you loaded your assembly from.
* mscorlib is a special case, you can't load it by way of managed code. You
can still access the currently loaded assembly by the mean of (sorry for the
c# code) typeof(int).Module.Assembly
Finally, don't forget that some namespaces are implemented in several dlls,
so you will have to load mscorlib.dll and System.dll to get a view of the
whole namespace.
As for members, could you show an example?

Signature
Sebastien Lambla
http://thetechnologist.is-a-geek.com/blog/
> Rahul,
>
[quoted text clipped - 161 lines]
> >
> >.