Okay. I'm not returning a true XML document, it's more like an XML
formatted string
that builds a GUI on the client. I'm not aware of Avalon or Xamlon GUI
tools being
hooked into DTDs to build a true XML document driven GUI interface.
With that being clarified; there is no string field being specifically
referenced to return a
'<string>' tag from the webservice. The webservice is returning :
<string><nicely formatted gui xml string that works fine outside the
webservice></string>
The point of the exercise was to build the gui on the fly through the
webservice. Not a
huge deal if for whatever it can't be done, however I am curious about the
source of the
string tag.
Hopefully that is a better picture of what is going on.
"Oleg Tkachenko [MVP]" <oleg@NO!SPAM!PLEASEtkachenko.com> wrote in message
news:Oj**************@TK2MSFTNGP11.phx.gbl...
Anthony P. Mancini wrote:
Looks like .NET webservices return XML encased between <string> and
</string> tags. Is there a way to make
that go away ?
I don't think there is something special about "string" tag itself. Most
likely it's your WSDL and web service implementation makes it so. If
"string" field is of string type, it cannot contain XML obviously,
that's why its content gets escaped.
--
Oleg Tkachenko [XML MVP, XmlInsider]
http://blog.tkachenko.com