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=76809 --- shadow/76809 2006-04-07 18:15:18.000000000 -0400 +++ shadow/76809.tmp.13996 2006-04-12 05:49:15.000000000 -0400 @@ -10,13 +10,13 @@ Component: CORLIB AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: -Cc: [EMAIL PROTECTED],[EMAIL PROTECTED] +Cc: [EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED] Summary: [PATCH] TargetInvocationException when calling Activator.CreateInstance Description of Problem: When calling Activator.CreateInstance(...), System.Reflection.TargetInvocationException occurs. @@ -264,6 +264,20 @@ It seems that RemotingServices.GetIdentityForUri and RemotingServices.GetServerTypeForUri need more love. I'm looking at it. + +------- Additional Comments From [EMAIL PROTECTED] 2006-04-12 05:49 ------- +Lluis, the 2nd patch broke the fix of the initial issue, +because if RemotingServices.GetServerTypeForUri ("app/obj") +returns null (like on MS.NET), MethodCall.ResolveMethod () +fails. + +We could either apply the first patch (which is quite non-intrusive) +and ignore this small incomptibility, or we need 2 +GetServerTypeForUri/GetIdentityForUri-like methods (one internal, +which accepts "app/obj" and another which doesn't). + +What's your opinion? + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
