Ian,
The idea behind plug-in architecture is that you have one interface, from
which all plugins must derive, and then instantiate. Your calling program
will then know what methods are available, and what to do with them.
This way all a program needs to know is the location of the plugin (easy if
you just enumerate through the .DLL files in a plugin folder say), then call
the methods on the interface, and let the plugin do it's thing.
Does that make sense?
I've got some code you can look at if you like...
http://www.dunesand.com/blog/developer/developer.htm
let me know if you need any more help with that.
Later.
Dan.
"Ian" <he******@hotmail.com> wrote in message
news:e7**************************@posting.google.c om...
Hi, I am writing an application and am creating a plug-in interface
for it.
The application will need to 'find' the plug-in's and will then need
to find all accessible methods.
The corresponding methods will need to have a corresponding 'user
friendly' name.
Eg: public void goForward() {...} will need to have a user friendly
name of "Go Forward"
I was thinking of creating an enumeration of custom objects (or maybe
string arrays ) that will store both the method name (for reflection)
and the associated friendly name.
This however seems a bit clunky. Am I on the right track or is there
any better way to do this?