Hi PeteZ,
Actually you should be able to just write a function header with the
class type in it just like you would any other .Net code that is not a web
service. Just pass the parameters as you would any other. .Net will then
handle it under the covers. I haven't had any problems with this so farand
I am constantly passing custom classes which are themselves build of other
classes nested many layers deep. So far no real problems. The one thing to
keep in mind is that the default test pages for your web service won;t work.
This is also no big deal as you just have to write a simple test harness of
your own.
Paul Michaud
"PeteZ" <pe***@aol.com> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...
Can someone help me here.
I'm having trouble finding details on how complex objects (eg. an object
created in a code behind page that has imbedded object references,
collections etc imbedded in it) can be sent via SOAP / HTTP to and from
remote web services
Its my understanding that there's a limit to what can be passed via SOAP /
HTTP ie. only native datatypes (I could be wrong)
I gather the data needs to be serializable before this can be done. What
is the easiest way to pass complex objects to and from web services ?
(a link or URL to some knowledge here would be helpful - tia)
thanks,
peteZ