Thanks for the quick fixes to the Xml classes. More than 2/3 of my errors are now gone :-) Most of the remaining errors comes from a repetitive xmlns attribute in elements.
Example: This is the Xml generated using the MS framework: <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#";><KeyName>Mono::</KeyName></KeyInf o> This is the Xml generated by Mono: <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#";><KeyName xmlns="http://www.w3.org/2000/09/xmldsig#";>Mono::</KeyName></KeyInfo> Both Xml fragment are equivalent - but make it hard to do direct string compare in the unit tests. Do we consider this a bug ? >From a Xml point-of-view this is equivalent, but if we strive a "perfect match" with the MS framework - then it isn't. Would it be hard to fix ? As for myself I can live with that (i.e. making changes to the test suites). Thanks again! Sebastien Pouliot Security Architect, Motus Technologies, http://www.motus.com/ work: [EMAIL PROTECTED] home: [EMAIL PROTECTED] ----- Original Message ----- From: "ginga(A.E.)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 30, 2002 12:37 PM Subject: [Mono-list] some System.XML bugfixes > I fixed some problems reported by David, Sebastien and ville. > Thanks. > > -- Atsushi Enomoto > > > _______________________________________________ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list > _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
