D
Drew Yallop
I read an XML file with a stream reader in VB.Net. When I
look at the stream reader output in debug mode (by
passing cursor over the stream reader object)the format
is a perfect replica of the file as displayed when I open
the xml file in VS .net 2003 IDE.
When I perform the same procedure in C# the stream reader
obkect displays a chaotic mess. Lots of whitespace after
and "\r" and "\n" after each element. The problem is that
I cannot perform any manipulation on this file in C#
because none of the Xpath strings work after the file is
loaded into an XmlDocument object nor when the
XmlDocument is passed to an XSLT transform, i.e. Xpath
can't find any of the elements, presumably because of all
the extra stuff in the stream. I do not have this problem
with the VB.Net procedure.
Does C# handle xml files differently?
Best regards,
Drew Yallop
look at the stream reader output in debug mode (by
passing cursor over the stream reader object)the format
is a perfect replica of the file as displayed when I open
the xml file in VS .net 2003 IDE.
When I perform the same procedure in C# the stream reader
obkect displays a chaotic mess. Lots of whitespace after
and "\r" and "\n" after each element. The problem is that
I cannot perform any manipulation on this file in C#
because none of the Xpath strings work after the file is
loaded into an XmlDocument object nor when the
XmlDocument is passed to an XSLT transform, i.e. Xpath
can't find any of the elements, presumably because of all
the extra stuff in the stream. I do not have this problem
with the VB.Net procedure.
Does C# handle xml files differently?
Best regards,
Drew Yallop