Why does my client throw exception “Invoke on non-existent proxy method”?
This problem can occur when the first parameter to Invoke is the current method name and not the return value from MethodBase.CurrentMethod(). When manually implementing a proxy method there are two method names involved: the name of the proxy method and the name of the XML-RPC method. These names are not necessarily the same, and if the first parameter of Invoke is the XML-RPC method name, and not the proxy method name, an exception is thrown with the message: “Invoke on non-existent proxy method”. This problem can be avoided by following these rules when using the method name with Invoke: • The call to Invoke always passes the name of the proxy method. • If the the name of XML-RPC method is not the same as the name of the proxy method, the XML-RPC method name is specified by passing it to the XmlRpcMethod attribute. The reason for this is that there are two stages of serialization when making an XML-RPC call. The first is performed by the implementation of the proxy method, convertin
