Remoting Server and Client in same application

I've tried all day to configure a service (server) and a client on the same ASP.NET application. Others seem to have the same problem. This exception is flipping me out:

RemotingException: The channel http is already registered.

When I call RemotingConfiguration.Configure() with both a and a element it registers the http channel twice. I've tried to put the server configuration into a separate config file, and call Configure twice with the same result.

I've also tried removing the delayLoadAsClientChannel in machine.config to register the "http client" channel with the client and "http server" channel with the server.

Using different ports for the server has no effect either. Using any other channel than http wouldn't work with IIS. I would assume that registering in code would probably work, but that's not an option.

I guess I'll just make a new virtual directory and put the server app into there, but there must be a way  to run an application both as server and client?

Update: I added some details here.

1 Comment

  • Hi,

    We have same kind of application, i.e. We have a .NET Remoting Server already running on IIS, and one ASP.NET application as Remoting client. These two are on different servers in different firewalls. Now we have another .NET Remoting Server which is on third machine, which needs to be accessed from .NET Remoting server. that means our .NET Remoting Server will act as client also. How to go with this ?

Comments have been disabled for this content.