Bug 3811 - DataContractJsonSerializer deserialization fails with subclass of List<int> as known type
Summary: DataContractJsonSerializer deserialization fails with subclass of List<int> a...
Alias: None
Product: Class Libraries
Classification: Mono
Component: System (show other bugs)
Version: 2.10.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-03-08 11:20 UTC by Rick Mohr
Modified: 2015-05-15 18:28 UTC (History)
2 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:


Description Rick Mohr 2012-03-08 11:20:04 UTC
The following code runs correctly on .NET 4.0, but fails with Mono:

using System;
using System.Collections.Generic;
using System.IO;
using System.Runtime.Serialization;
using System.Runtime.Serialization.Json;
using System.Text;

namespace MonoDeserializationFailure
    class Program
        static void Main(string[] args)
                var knownTypes = new List<Type> { typeof(IntList) };
                var serializer = new DataContractJsonSerializer(typeof(ListOfNumbers), knownTypes);

                string json = "{\"Numbers\": [85]}";
                using (var stream = new MemoryStream(UTF8Encoding.Default.GetBytes(json)))
                    var nums = (ListOfNumbers)serializer.ReadObject(stream);
                    Console.WriteLine("Success: " + nums.Numbers.Count);
            catch (Exception ex)
                Console.WriteLine("Failure: " + ex.Message);

    public class ListOfNumbers
        public IntList Numbers;

    public class IntList : List<int>
Comment 1 Miguel de Icaza [MSFT] 2015-05-15 18:24:41 UTC
This is fixed;   Test added as well to Mono/master
Comment 2 Miguel de Icaza [MSFT] 2015-05-15 18:28:17 UTC
Tests are here: mono/f1778d1797ad80109890c2cbcb76b1e2b8e08b05

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Note You need to log in before you can comment on or make changes to this bug.