It sounds like what you want to do is register and unregister remote objects
on the fly. If that's the case, they way you would do that is using
RemotingServices.Marshal() (to make an object available for remoting) and
RemotingServices.Disconnect() (to disconnect a remoted object). If you go
with this, be sure to remove any <wellknown> tags from your config file
first since this type of declarative syntax will not allow you to disconnect
the object when it's no longer needed/wanted.
If you need additional information, feel free to post in the
microsoft.public.dotnet.remoting newsgroup since it's dedicated to
remoting-related issues.
Ken
"Matt Kosorok" <Ma*********@discussions.microsoft.com> wrote in message
news:87**********************************@microsof t.com...
After executing RemotingConfiguration.Configure( myConfigFile ) the http
channel is now in use. To terminate this instance I have to shut down the
application, which then frees up the resources taken up by whatever the
configuration file indicated. I'd like to be able to add and remove
instances as I please. For instance, in a gui. Say I've added a remoting
object. Now I want to terminate that remoting object. I want to be able
to right click on it, select terminate, and have it free up that http
channel, etc. How do I terminate that remoting instance?
--
- Matt Kosorok