AppDomains are very useful when building extensible apps that use a plugin
architecture. By loading a plugin into a separate app domain, it allows you
to unload the plugins and also give you a lot of control over the run-time
security capabilities of the plugins.
Once you start using AppDomains, you might consider a controller class to
simplify the manipulation and interaction with the code loaded into the
other AppDomains. Basically, create the AppDomain, load the controller class
into it, and then use the members of the controller class to manage the
plugins that are loaded into the AppDomain and pass data back and forth.
Regards
Allen
"David Elliott" <Da**********@BellSouth.net> wrote in message
news:qv********************************@4ax.com...
I have written an application and am looking to extend its capabilities.
I am looking to create pluggins and don't know where to start. I am also looking to store the
pluggins in a subdirectory from the application root.
I looked on MSDN and some of the other code sites but couldn't find and
example. Does anyone have an example?
Thanks,
Dave
Da**********@BellSouth.net
