C# Object Serialized using Newton.JSON is Empty

Question

I am having trouble in serializing an Object using Newton.Json, when I used breakpoints to debug, I found my serialized object is empty while the object provided to serializer is intact.

I have attached the Screen Shots.

EDIT : Here is the Class whose list I am trying to serialize.

class ArgumentGroup
{
    String argumentGroupName = "";
    String argumentDescription = "";
    int argumentCount = 0;
    List<Argument> argumentList = new List<Argument>();

    public ArgumentGroup(string argumentGroupName, string argumentDescription, int argumentCount, List<Argument> argumentList)
    {
        this.argumentGroupName = argumentGroupName;
        this.argumentDescription = argumentDescription;
        this.argumentCount = argumentCount;
        this.argumentList = argumentList;
    }
}

add this: `var obj = new ExampleClass(); var jsons = JsonConvert.SerializeObject(obj, new JsonSerializerSettings() { NullValueHandling = NullValueHandling.Ignore });` — Mojtaba Nava, Oct 14 '19 at 11:12
Use public properties, not fields. Fields are implementation details, only *properties* are part of the class's interface. Serializers (all of them) work with properties. They can be configured to work with fields as well, even private fields, but they *shouldn't* unless there's a very important reason — Panagiotis Kanavos, Oct 14 '19 at 11:17
This - `String argumentGroupName = "";` is *private*, and thus won't be serialized. Make it `public` and it should work. — Lasse V. Karlsen, Oct 14 '19 at 11:41

Vijaykumar Handargule · Accepted Answer · 2019-10-14T11:26:29.697

1

Make your fields public, because default NewtonSoft.Json will only serialize public members or for some reason you really don't want to make your fields public, you can use the JsonPropertyAttribute to allow them to be serialize and deserialize.

edited Oct 14 '19 at 11:26

answered Oct 14 '19 at 11:15

Vijaykumar Handargule

36
4

2

Public fields are a bad idea - fields are implementation details. Serializers are meant to serialize *properties*. – Panagiotis Kanavos Oct 14 '19 at 11:16
yes so that is why added "or for some reason you really don't want to make your fields public, you can use the JsonPropertyAttribute to allow them to be serialize and deserialize." – Vijaykumar Handargule Oct 14 '19 at 11:31
@PanagiotisKanavos I agree that public fields is a bad idea, but it *would* make them appear in the json. – Lasse V. Karlsen Oct 14 '19 at 11:42

score 0 · Answer 2 · answered Oct 14 '19 at 11:20

0

Does JsonProperty have each class property?

[JsonProperty("argumentGroupName")]
public string argumentGroupName { get; set; }

and import:

using System;
using System.Collections.Generic;

using System.Globalization;
using Newtonsoft.Json;
using Newtonsoft.Json.Converters;

answered Oct 14 '19 at 11:20

Ahmed Msaouri

316
1
10

There's no reason for `JsonPropert`, JSON.NET serializes all properties by default – Panagiotis Kanavos Oct 14 '19 at 11:23
2

JSON.NET serializes just the public properties by default, not all properties !!!! – Ahmed Msaouri Oct 14 '19 at 11:33
You used a public property which means `JsonProperty` isn't needed – Panagiotis Kanavos Oct 14 '19 at 11:37

C# Object Serialized using Newton.JSON is Empty

2 Answers2