.Net Remoting 接口重载方法

Question

We have a legacy app that uses.Net Remoting (we will soon convert it to use something better)

We have had an interface dll, shared between client and server, that looks like this

[ServiceContract]
public interface ExampleInterface
{
    [OperationContract]
    List<DataObject> InterfaceMethod(string strParam);
}

About two months ago, we needed a few more parameters so we created a ParameterObject and added a new overloaded function to support it; while leaving in the old function for older clients. So the interface now looks like:

[OperationContract]
List<DataObject> InterfaceMethod(string strParam);
[OperationContract]
List<DataObject> InterfaceMethod(ParameterObject parameter)

We have deployed the update and we are getting reports that when older clients try to call the method with the string parameter, an exception is thrown with the message 'Cannot resolve the invocation to the correct method' . The server's exception stack trace is 100% remoting code.

I was able to reproduce in house and changing the newer method to a different name solved the issue, but this would mean we would have to update a lot of customers.

Is method overloading not possible in.Net Remoting? Are there any work-arounds to this?

Note : we have several working Remoting interfaces that overload methods, but they all have differing parameter counts, perhaps remoting cannot distinguish between two methods with the same name and same parameter count?

Answer 1

Not sure if this is related to the question. Ran into the same error in a production environment that uses .NET remoting (no method overloading). Found out that one of the reference assemblies were of earlier version than the one used during development.