[Mono-bugs] [Bug 610036] New: Data Contract Serializer throws exception when adding a custom dictionary to KnownTypes collection

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=610036

http://bugzilla.novell.com/show_bug.cgi?id=610036#c0


           Summary: Data Contract Serializer throws exception when adding
                    a custom dictionary to KnownTypes collection
    Classification: Mono
           Product: Mono: Class Libraries
           Version: SVN
          Platform: PC
        OS/Version: Ubuntu
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: tebjan at vvvv.org
         QAContact: mono-bugs at lists.ximian.com
                CC: atsushi at ximian.com
          Found By: Development
           Blocker: No


Created an attachment (id=365626)
 --> (http://bugzilla.novell.com/attachment.cgi?id=365626)
a mono project to compile/run the test application

Description of Problem:

Contract Serializer throws exception when adding a custom dictionary to the
KnownTypes collection.

Steps to reproduce the problem:

1. Run the application in the bin\Debug folder in the provided .zip with mono

Actual Results:

console output showing the data before serialization
exception from the serializer
empty test.xml

Expected Results:

console output showing the data before serialization
a test.xml file with the same data as the test_NET_ReferenceOutput.xml
console output showing the data after serialization

How often does this happen? 

each time the application is started

Additional Information:

we encountered this bug in a larger project, which has to serialize a much
bigger data graph then the provided one in the attached test project. it
appears on windows mono 2.6.4 and also on linux ubuntu with mono 2.7 compiled
from SVN.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.