I'm reposting a previous post here with a more descriptive subject,
which will hopefully get a bit more attention.

My issue is this:
I am calling a remote object over TCP from a pooled .NET Serviced
Component (COM+ component). Because this component (which will be the
Remoting client) is really a stateless component (and there could be
several of the component in the application pool), I am questioning
the best place to register and unregister the client tcp channel.  I
assume I should either create or register a single channel that is
static to the component, or I should register and unregister the
channel explicitly ever time I need to call the remote object.

HOWEVER, I noticed in my test code that I was able to completely
remove the explicit channel registration, and everything still seemed
to work fine!  Can anyone explain this?  I am using
Activator.GetObject() to create the proxy for my remote object, as so:

MyObject myObj = (MyObject)Activator.GetObject(
 typeof(MyObject), "tcp://server:port/ObjectName");
myObj.MyMethod();

Perhaps (as Sunny suggested in my previous post) channel registration
is only required when using events/delegates?  Strangely, I have yet
to see an example where someone doesn't explicitly register a channel
on the client.  I wonder if the Activator.GetObject() method is
actually creating and registering a default channel for me?  It would
be nice not to have to worry about explicitly registering and
unregistering channels if I don't need to, but at the same time, I
don't want to deploy this code that seems to magically work (despite
what I have been reading) and have it not work all the sudden when it
is deployed in a production environment.

Any info is appreciated.

Steve