I forgot to ask: why are you using the tcp channel with the soap formatter? I can't think of a scenario where that channel/formatter combination makes sense.
If you're trying to specifically interoperate with an older soap toolkit type of client, you'd be using http/soap. If you're just trying to get your own two .net apps to talk, you're better off with tcp/binary (between two apps on the intranet) or for scenarios where the server is behind a firewall that only has port 80 open, http/binary with the server hosted in IIS/ASP.NET. -Mike DevelopMentor http://staff.develop.com/woodring > > -----Original Message----- > From: Moderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Ned > Sent: Thursday, June 26, 2003 1:51 AM > To: [EMAIL PROTECTED] > > Hey Mike, > > here is the info you asked for: > Please note: I'm developing with .NET Framework 1.1 therefore >
