Xml Bug in .net framework 2.0




i have a well formed xml file which works perfectly with .net framework 1.1.
Unfortunatly i got an exception with .net framework 2.0 beta 2.

XmlDocument doc=new XmlDocument();

System.Xml.XmlException: The 'FS32Texttyp' start tag on line 277 does not
match the end tag of 'FS32p'. Line 277, position 24./ at
System.Xml.XmlTextReaderImpl.Throw(Exception e)/ at
System.Xml.XmlTextReaderImpl.Throw(String res, String[] args)/ at
System.Xml.XmlTextReaderImpl.ThrowTagMismatch(NodeData startTag)/ at
System.Xml.XmlTextReaderImpl.ParseEndElement()/ at
System.Xml.XmlTextReaderImpl.ParseElementContent()/ at
System.Xml.XmlTextReaderImpl.Read()/ at
System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)/ at
System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)/ at
System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean
preserveWhitespace)/ at System.Xml.XmlDocument.Load(XmlReader reader)/
at System.Xml.XmlDocument.Load(Stream inStream)/ at
Funworld.Data.Text.Load(String language, String configName, String path)/

The Xml File looks like this:


Does anyone know this problem?





i found another xml issue:

The 'HudInfoMoveTime' start tag on line 182 does not match the end tag of

The strange thing is that the XML file looks perfecty like this:

The assembly is compiled with VS.Net 2003, so it is a 1.1 assembly. I have
installed the 2.0 framework and set the registry value that every
application should use the newest framework. This works fine except the xml
problem ...



more information:

The problem happens in all different kind of XML files. All the problems
have one thing in common:

The broken XML name occurs in an UTF-8 encoded file on the file position
0x1FF? - 0x1FFF. This means that some characters from the node name are cut
from the full name exactly at this fileposition.

eg. is i have this error message:
System.Xml.XmlException: The 'FS32Texttyp' start tag on line 277 does not
match the end tag of 'FS32p'. Line 277, position 24

the missing substring "Textty" is exactly on position 0x1FFA to 0x1FFF. In
all cases the character at file position 0x2000 is recognized by the xml
parser again.





Shame on me, it's not a bug of the .net framework 2.0 beta 2.

The problem is a none working stream that we were using in our software.

..net framework 1.1 called the "Read" method of the stream allways with
offset 0.
..net framework 2.0 calls the "Read" method of the stream with offset>0.

The stream that we were using did not work correctly with offsets > 0. So
the problem was never noticed on 1.1 framework and now on 2.0 framework we
saw this problem for the very first time.

sorry for my wrong post.


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question