Application - Object Browser interface.
Alright, I must admit that I am an object browser addict. Is it a Dll that an be called by another application?
Alright, I must admit that I am an object browser addict. Is it a Dll that an be called by another application?
If you mean the "Object Browser" view from Visual Studio then no... that's VS stuff, not part of the framework. It doesn't even seem to be a .NET thing...
you can write your own Object Browser using reflection. here is a tutorial
http://www.programmersheaven.com/2/Dot-Net-Reflection-Part-1
Jack thank you so much for the reference!
I'm good but I don't think I'll be able to write anything that nice - this year. :)
Does the object Browser use reflection? It is slow and reflection is slow. It has to be looking at classes etc. And it has a lot of text so isn't it doing more than just reflection?
It could be that the Object Browser uses the native metadata interfaces instead of .NET reflection. Not only that probably this is faster but it also avoids actually loading the assemblies.
As for the text that probably comes from the xml documentation files. I don't know if there is an API for reading those files but since they are XML probably it's not a problem to read them.