.NET Framework Bookmark and Share   
 index > ASMX Web Services and XML Serialization > XML Document versus String parameter
 

XML Document versus String parameter

Hello.

I want to publish a web service with an untyped parameter.

¿Which is the best option, a XML (XML.Document or XML.Node) parameter or a String parameter (this parameter is really a XML)?

Why?

Thanks in advance.
  • Edited byFran-1980 Tuesday, September 08, 2009 9:23 PM
  •  
Fran-1980
In general XmlDocument or XmlNode is preferable to string. Even better is the XElement class, but that requires .NET 3.5
-steve
Brain.Save() -- http://hyperthink.net/blog
Steve Maine
In general XmlDocument or XmlNode is preferable to string. Even better is the XElement class, but that requires .NET 3.5
-steve
Brain.Save() -- http://hyperthink.net/blog
Steve Maine
Please, Why?
Fran-1980
Because they follow the rules of valid XML. A string does not.

John Saunders
WCF is Web Services. They are not two separate things.
Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
Use File->New Project to create Web Service Projects
John Saunders

You can use google to search for other answers

Custom Search

More Threads

• Unable to add web reference in VS 2005
• Webservice Scalability Problem
• how to use the pre-compiled generated serialization assemblies to serialize/deserialize an array of my objects?
• Server side AzMan roles mismatch roles seen by Client Application Services
• How have been used the Microsoft Dynamic DHTML Editing control?
• DIME attachment in Web Service Causing Invalid Character 0X0C Line 1 Position 1 in Response to Client
• problem : dll not generated to webservice with Visual Studio 2005
• inserting break points in aspx.file
• Error generating XMl Document
• Problem with XmlSerialization of Nullable Types