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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=77191 --- shadow/77191 2006-01-16 16:19:06.000000000 -0500 +++ shadow/77191.tmp.18568 2006-01-17 01:43:07.000000000 -0500 @@ -272,6 +272,34 @@ RemotingServices.ExecuteMessage(...)). But in real tests such assumption is not confirmed (for Mono test from my first report works succesfuly in case of ContextBoundObject). Am I missed something, or does Mono use separate dispatching mechanisms for ContextBoundObject and channel based invokations? + +------- Additional Comments From [EMAIL PROTECTED] 2006-01-17 01:43 ------- +The methodBindings are indeed + +static readonly BindingFlags methodBindings = +BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic; + +Hence no wonder about the ambiguity ;-) + +The naive thought to remove BindingFlags.NonPublic fixes this bug, +but it also breaks the activation unit tests regarding +WellKnownServices: + +1) MonoTests.Remoting.ActivationTests.TestCreateTcpWkoSingleCall : +2) MonoTests.Remoting.ActivationTests.TestCreateTcpWkoSingleton : +3) MonoTests.Remoting.ActivationTests.TestCreateHttpWkoSingleCall : +4) MonoTests.Remoting.ActivationTests.TestCreateHttpWkoSingleton : +System.InvalidCastException : Cannot cast from source type to +destination type. +in [0x00188] (at +/usr/src/mono/head/mcs/class/corlib/System.Runtime.Remoting.Proxies/RealProxy.cs:219) +System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke +(System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, +System.Exception exc, System.Object[] out_args) + + +I'm looking at this. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
