Urs Muff <[EMAIL PROTECTED]> writes: > I would strongly recommend (and Ingo does too) to create a metadata library > with interfaces. This assembly only contains all the interfaces and you can > easily use the same assembly on the client and on the server. The server is > then implementing those interfaces. Here is a sample (and that works fine): > [...]
Hi Urs, I do appreciate your taking the time to write a fairly lengthy answer, and I understand your comments regarding interfaces, but that wasn't really the question I was trying to answer. I was trying to understand why the proxy generated by SoapSuds doesn't work. At the moment, I'm just trying to understand the pros and cons of the various .NET remoting options. (And if one of the cons of SoapSuds is that it simply doesn't work, then I guess that's a useful thing to know.) As far as an interface library goes, that may not be the best approach in our case. We have a set of library classes that will normally be called directly, but may sometimes be called remotely, and the application code would tend to be the same in each case. Thanks, Alasdair > > -----Original Message----- > > From: Alasdair Mackintosh [mailto:[EMAIL PROTECTED] > > > > [...] > > Using a client compiled against a SoapSuds generated proxy, I'm unable to > > invoke any server-side method that returns an instance of another > > server-side class. > > [...]
