Using XML & ASP.NET (or what do I *need* to know?)
- From: Karl <kthompson@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Sep 2005 05:55:29 -0400
I'm trying to learn an acceptable way to marshal complex data between an ASP.NET web service and an ASP.NET web client. Initially, it will be enough for the client to display the data from the service, but eventually, I'll have to write a client that will allow for modification of the data and return it to the service.
I gather from bits and pieces that I'm reading that I can convert the data into an XML document and it is this document which is sent to the client over an HTTP connection. Is this assumption correct?
If so, what's the best way to convert the data into XML? Specifically, I have multiple instances of a class managed by a linked list.
I've been fooling around with XmlSerializer (System.xml.serialization), since that seems as if it will convert the class instances to formatted XML. On the other hand, the docs for XmlSerializer only talk about writing the XML to a file, which is not what I want to do.
Can someone put me on the right track please? (Ultimately, do I want to write a web method in the service which returns an XML document?
TIA. .
- Follow-Ups:
- Re: Using XML & ASP.NET (or what do I *need* to know?)
- From: Martin Honnen
- Re: Using XML & ASP.NET (or what do I *need* to know?)
- Prev by Date: SAX (Simple API for XML) and SOAP
- Next by Date: Re: SAX (Simple API for XML) and SOAP
- Previous by thread: SAX (Simple API for XML) and SOAP
- Next by thread: Re: Using XML & ASP.NET (or what do I *need* to know?)
- Index(es):
Relevant Pages
|