[Mono-bugs] [Bug 75626][Wis] New - System.Runtime.Remoting.Channels.Tcp.TcpChannel() works incorrectly

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by mail at meebey.net.

http://bugzilla.ximian.com/show_bug.cgi?id=75626

--- shadow/75626	2005-07-24 18:21:40.000000000 -0400
+++ shadow/75626.tmp.20295	2005-07-24 18:21:40.000000000 -0400
@@ -0,0 +1,38 @@
+Bug#: 75626
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: mail at meebey.net               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: System.Runtime.Remoting.Channels.Tcp.TcpChannel() works incorrectly
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+
+The TcpChannel() constructor works different on Mono than on MS .NET.
+On Mono it will call the TcpChannel(0) which means a server channel is created.
+On MSDN it says when the () ctor is used _only_ a client channel is
+registered, no server channel.
+
+Here the MSDN doc of TcpChannel constructors:
+http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemRuntimeRemotingChannelsTcpTcpChannelClassctorTopic.asp
+
+Looking at the Mono source I see that the TcpChannel(int) ctor checks if
+the port is != null, which will never be case when I use "new TcpChannel()"
+because it will call base(0).
+
+So changing the () ctor to not set the port 0 would fix this.
+
+Result is that my application with remoting works on Mono but not on MS
+.NET because there is no server channel because I am using the () ctor.