AppDomains and Remoting

From: Tibby (tierscheiss1977_at_hotmail.copm)
Date: 03/01/05 

Date: Tue, 1 Mar 2005 11:00:58 -0800

I think I'm barking up the right tree. Here's my plan:
Make some nice plugins, and load those plugins into a
seperate AppDomain. When there's an update to the plugin
(s), unload the Plugin AppDomain, and reload it, leaving
the main AppDomain intact and running. My question is,
how to I make calls to functions in these plugins from
the main AppDomain, and how would I load a form that is
in one of these plugins?
I also have another peice of this puzzle. I have an
updater program that downloads the encrypted files from
my server, and updates the main program. is there a way
I can load this into it's own AppDomain, and hand control
over to this new AppDomain, and unload my origional one
so I can update the files, then reverse the process?
Like I said, maybe I'm barking up the wrong tree, or I'm
trying to bite off way to much, but I have a program that
I need the lowest amount of down-time that is physically
possible, while being able to support upwards of 5
software updates to the plugins a week.

Thanks,
Tibby

Relevant Pages

  • Re: Cross domain performance
    ... I will assume there is no solution and I have to load the plugins in the ... main appdomain in order to perform at a respectable level. ... Calling in to these interfaces is what is slowing me down. ...
    (microsoft.public.dotnet.framework.performance)
  • Re: Thank you and goodbye Mr Peter Morris
    ... I have only encountered one time the absolute need to load plugins into ... was loaded into its appdomain, it would simultaneously take all new requests ... There's a good book that discusses this in depth: "Customizing the .NET ... find in the Customizing the .NET Framework CLR book is not easily ...
    (borland.public.delphi.non-technical)
  • ApplicationDomains
    ... Create new appdomain to "discover" all plugins and report them back ... Destroy discovery domain (To free assemblies/resources) ... I plan to use this in a service project, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: ApplicationDomains
    ... Basically, here's my plan: ... > 2) Create new appdomain to "discover" all plugins and report them back ... > 3) Destroy discovery domain (To free assemblies/resources) ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Checking for implementation of an interface
    ... >> which plugins they want to run from a list of available plugins. ... If I load ... >> each assembly and check it, then I have all those assemblies in memory until ... >> into the separate appdomain. ...
    (microsoft.public.dotnet.framework)
Loading