[Mono-bugs] [Bug 77520][Nor] New - TcpChannel.Parse returns incorrect objectURI

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Feb 9 19:40:15 EST 2006

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 art.sherwood at medsphere.com.


--- shadow/77520	2006-02-09 19:40:15.000000000 -0500
+++ shadow/77520.tmp.6446	2006-02-09 19:40:15.000000000 -0500
@@ -0,0 +1,39 @@
+Bug#: 77520
+Product: Mono: Runtime
+Version: unspecified
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: remoting
+AssignedTo: lluis at ximian.com                            
+ReportedBy: art.sherwood at medsphere.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: TcpChannel.Parse returns incorrect objectURI
+Description of Problem: TcpChannel.Parse behaves differently on mono than
+it does on ms.net.  This causes client-activated binary remoting to fail on
+linux when RemotingConfiguration.ApplicationName is assigned.
+Steps to reproduce the problem:
+1. TcpChannel chan = new TcpChannel();
+2. string s;
+3. chan.Parse ("tcp://localhost:8787/AppName", out s);
+Actual Results:
+s == "AppName" (on linux)
+Expected Results:
+s == "/AppName" (on windows)
+How often does this happen? 
+Additional Information:
+TcpChannel.ParseTcpURL should include the leading slash in the objectURI.

More information about the mono-bugs mailing list