Anyone know of a good source on how to debug a remoting service running on
another server?

[quoted text, click to view]
Ray,

I'm sorry, I can't help you with your direct question, but I can offer
our modus operandi in the hope that it will help.

Firstly, when we develop remotable objects, we include projects for
local and remote clients. These are practically identical, except that
the former calls the object locally and the second calls it remotely.
They contain methods that exercise all the public methods of the remote
object.

So all initial debugging is done locally (i.e. without remote calls).
That means that any problems that arise later are to do with remoting
and not with the logic of the methods themselves.

We then install the remoting service locally (on the developer's
machine) and use the remote client to test the installation there. Once
we can use it successfully in this way, we deploy it to the remote
machine and use the remote client on the developer's machine to call it.

We configure remoting services using configuration files. This means
that we only need to edit these files to make calls to the appropriate
machine. For example, the client config file will refer to localhost
during testing on the developer's machine. Once the object is deployed
to the remote machine, the config file is just edited to point to the
remote box. This means no changes to code are necessary - which
drastically reduces the margin of error.

Obviously, I've left out a lot of detail (like delay signing, final
signing, deployment to the GAC, deployment of config files, etc, etc).
If you would like more info, please let me know and I'll see what I can do.

HTH