Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=77117 --- shadow/77117 2005-12-29 06:24:11.000000000 -0500 +++ shadow/77117.tmp.16531 2005-12-29 06:24:11.000000000 -0500 @@ -0,0 +1,33 @@ +Bug#: 77117 +Product: Mono: Class Libraries +Version: 1.1 +OS: +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Normal +Component: Sys.XML +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: XmlSchemaExporter never marks types nillable + +If you use System.Xml.Serialization.XmlSchemaExporter to create XML +Schemas for types, then the elements in the generated XML Schema will +never have nillable set to true. + +Nillable should only be false for value types and XmlQualifiedName (on +1.0 profile only). + +I've attached the source code of a small test application that allows you +to reproduce this issue. + +Note: MS.NET always output complex types before elements, while we do the +oppositive (I'll probably post a patch for that later). The test program +checks for the output that is expected on MS.NET, so you'll get more +differences than only the nillable difference, but you can safely ignore +the other differences. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
