I actually used .soap in both web.config and in the code. It's just that I started to write the reply and then decided to try .rem and then finished the reply. So I accidently copied part of the new code. Sorry about that. But I tried it once again just to make sure.
If I configure IIS to listen to port 8080 I get a long delay and then the following SoapException: 'Additional information: An existing connection was forcibly closed by the remote host'. I don't see how any application (whether IIS or aspnet_wp) could be listening on port 8080 if I don't configure IIS to listen to this port. And if I do, I assume that IIS wont understand anything but Http. When does IIS start the aspnet_wp so it can listen on port 8080? IIS has to somehow read my web.config. But how can it do that if I don't use http on a port IIS is listening to? Thanks for your patience, but I just don't get it. Peter From: "Deepak Rao" <[EMAIL PROTECTED]> > I am just going to reiterate what Mike was saying - IIS is not doing > anything to host your object on a TCP channel. It is only starting the > ASP.Net worker process, which just happens to call > RemotingConfiguration.Configure(). It is no different than you creating > an exe and calling Configure(). > > I see one problem with your code. You are using DBRemote.rem as the URI > for the remote object. But the remote object is available as > DBRemote.soap. So change this line under the TCPChannel > > string url = "tcp://" + Server + ":8080/DBRemote/DBRemote.rem"; > > to > > string url = "tcp://" + Server + ":8080/DBRemote/DBRemote.soap"; > > The only reason you need the .soap extension is so IIS can use the > HTTPHandler registered for the .soap extension. In the case of the > TCPChannel, it doesn't really matter what the extension is. IIS is in no > way involved with hosting your object on the TCPChannel. > > Hope this helps > > Deepak You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
