I believe its described in that WSDL schema stuffs VS.net generates for your web service. It doesn't need the code for the method, just the prototype. look at the .wsdl file from your project
Lovingly Yours, Elan Hasson http://www.compiled.org -- The Programmer's Resource -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of Farhan Shah Sent: Wednesday, July 03, 2002 8:41 AM To: [EMAIL PROTECTED] Subject: Complex Objects and Webservice I can create a Web Service using very simple return types; for example, strings and integers. I would like to return a complex object to the calling client if possible (Meaning an object I wrote myself). Obviously, I can pass a delimited string to the client and build the object on that end, but I would prefer to just pass the object as I would with all my other code. Although my Web Service can return a complex object, I don�t know how to tell the compiler on the client-side about the details regarding the object. Below is an example of my goal: Dim MyObjectBroker as ObjectBroker = new ObjectBroker() Dim MyWidget as Widget = MyObjectBroker.GetWidget() MyWidget.SomeMethod() The client doesn�t know about the SomeMethod(); therefore, I get a compiler error. I always use Option Strict. I should seemingly be able to tell the client about the implementation of the object, and have the dynamic details go over the wire. I am off the mark on this idea? I am using the Web Service incorrectly? Any insight would be greatly appreciated. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
