DotNetters, I seem to miss something when I used SOAPSUDS. Trying to keep OO design guidelines in mind, I only want to return interfaces. So I have a core.dll containing only the serializable classes I want to transfer to the client, an interfaces.dll containing only the interfaces of both those elements and my Marshalled-by-reference 'manager' object, a server.exe implementing the manager object, and a client.
Now, the server needs both the core.dll and the interfaces.dll. I grok that. The client needs only the interfaces.dll to compile, but gives a runtime error "Additional information: Parse Error, no assembly associated with Xml key" if is does not have the core.dll. I grok that as well - it needs a kind of implementation beneath the interfaces it recieves, for the objects the client receives are 'bodily' serialized, so to speak. Enter soapsuds. I generated a soapsuds.dll from the URL and I see to my delight that ILDASM says that both my element manager and its interfaces, as well as the interfaces for my serializable objects are present. So I give the client a reference to the soapsud.dll. The same error as before when the core was missing, so I add the core again. Next I get: "An unhandled exception of type 'System.InvalidCastException' occurred in mscorlib.dll Additional information: Return argument has an invalid type." When I move my mouse cursor over the offending line, it says that the function returns a "System.Runtime.Remoting.Proxies.__TransparantProxy" in stead of my desired interface. Any clues to what goes wrong? I desired, I can mail the whole project. Regards Joost van Schaik You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
