Well, I know that various version of the parser get upset
with things
inside of <>'s, and try to parse them as element
names. You've got at
least one in there with a comma in it (<Start sequence,
176 bytes>). Try
taking the comma out of that 'element' and see if that
'fixes' it.
If it does, then before you feed this into an XML parser of
any sort,
you'll need to run it through something that escapes XML
text. Names of
such methods escape me at the moment.
_____
Peter Smith
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "DotNetDevelopment, VB.NET, C# .NET,
ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting"
group.
To post to this group, send email to DotNetDevelopment googlegroups.com
To unsubscribe from this group, send email to
DotNetDevelopment-unsubscribegooglegroups.com
For more options, visit this group at
http:
//cm.megasolutions.net/forums/default.aspx
-~----------~----~----~----~------~----~------~--~---
|