Hi
I added a new test for exporting of a typed DataTable and a typed
DataSet by the same XmlSchemaExporter and a fix for the
XmlSchemaExporter.
Generated typed DataTable and typed DataSet have an identical schema and
an identical TargetNamespace. This fix is a workaround for this specific
Hi all,
I fixed IXmlSerializable.ReadXml implementation in the DataTable class.
And removed Ignore attribute from the tests that failed before this
fix.
Please review.
Thanks.
SystemDataReadXml.patch
Description: SystemDataReadXml.patch
___
Hello,
this is the new code, posted for review.
The reason for the rewrite is explained in the comment here:
https://bugzilla.novell.com/show_bug.cgi?id=319930
Now that monster piece of code (point [4] in the comment) is
gone, and the new code is hopefully easy to understand.
The patch still
Hi all,
I think we isolated the problem with the crossAppDomain memory problem.
It looks like the problem comes from passing lists between appdomains.
If we pass a list of classes / objects across appdomain boundries,
the memory usage sky rockets.
Even accessing a list.Count, causes the
Hello,
You cannot add reference to System.Data.dll when building
System.Xml. Add your DataSet related test under System.Data.
The fix itself looks ok, except for coding style. I don't think
it was your first contribution though ...?
http://www.mono-project.com/Coding_Guidelines
Atsushi Eno
Congratulations to all on getting Mono to beta status as a scripting engine for
Second Life.
I have been following Second Life integration all along and am impressed with
what it required, including memory usage, leaks, and stability. Second Life is
a very demanding application, quite
