JavaScriptSerializer [ScriptIgnore] not effective on virtual properties?

Question

I have returning a Json(myObj) action result. The myObj is of type Badge

The only two objects that Badge has that could cause a loop from a serializer, are:

public class Badge
{
    public Badge() { }

    public Badge(String Name, String Description)
    {
        this.Name = Name;
        this.Description = Description;
    }

    [ScriptIgnore]
    public virtual BadgeType BadgeType { get; set; }
    [ScriptIgnore]
    public virtual ICollection<User> Users { get; set; }

    public int ID { get; set; }
    public string Name { get; set; }
    public string Description { get; set; }
    public string PrerequisiteCriteriaRef { get; set; }

    //PrerequisiteID

    public static Badge CreateForSeeder(BaseDBContext db, String Name, String Description, int TypeID)
    {
        Badge b = new Badge();
        b.Name = Name;
        b.Description = Description;
        b.BadgeType = db.BadgeTypes.Where(x => x.TypeID == TypeID).FirstOrDefault();
        return b;
    }
}

Which I've given the attribute, but it's not helping out at all...?

score 13 · Answer 1 · answered Feb 23 '15 at 15:06

13

You should set ApplyToOverrides parameter of ScriptIgnore to true:

[ScriptIgnore(ApplyToOverrides = true)]

answered Feb 23 '15 at 15:06

lxa

3,234
2
30
31

score 4 · Answer 2 · answered May 02 '17 at 19:13

The problem here is that your virtual parameters are override into a Dynamic created class. In this case the [ScriptIgnore]attributes are overriden also.

that is why you should use [ScriptIgnore(ApplyToOverrides = true)], in order to keep the [ScriptIgnore] attribute valid into derived classes.

score 1 · Accepted Answer · edited Feb 16 '18 at 19:18

The JavaScriptSerializer (which is what is used when you return Json) definitely honors the [ScriptIgnore] attribute.

Here's a proof:

Model:

public class User
{
    public Badge Badge { get; set; }
}

public class Badge
{
    [ScriptIgnore]
    public virtual ICollection<User> Users { get; set; }

    public int ID { get; set; }
    public string Name { get; set; }
}

Controller:

public class HomeController : Controller
{
    public ActionResult Index()
    {
        var badge = new Badge
        {
            ID = 1,
            Name = "badge"
        };
        var user = new User
        {
            Badge = badge
        };
        badge.Users = new[] { user }.ToList(); 

        return Json(badge, JsonRequestBehavior.AllowGet);
    }
}

If you remove the [ScriptIgnore] attribute from the Users property you will get a circular reference error.

So I guess that your problem is somewhere else.

But personally I would recommend you using view models instead of those [ScriptIgnore] attributes.

So you simply define a view model that will contain only the properties you need for the given view:

public class BadgeViewModel
{
    public int ID { get; set; }
    public string Name { get; set; }
}

and then in your controller action you map between the domain model and the view model and you pass the view model to the view:

public class HomeController : Controller
{
    public ActionResult Index()
    {
        Badge badge = ...
        BasgeViewModel vm = new BasgeViewModel
        {
            Id = badge.Id,
            Name = badge.Name
        };

        return Json(vm, JsonRequestBehavior.AllowGet);
    }
}

and if you are sick of writing mapping code in your controllers you simply head over to your NuGet package console and type the following command:

Install-Package AutoMapper

in order to take full advantage of the excellent AutoMapper library.

For some reason I thought View models were a redundant approach, I'll read some pages, do some research. Clear I'm wrong, sounds like it could be JUST what I need. To solve THIS problem & issues I'm having with my validation (which you also commented on). Thank you Darin, great post! — williamsandonz, Aug 18 '12 at 08:32

JavaScriptSerializer [ScriptIgnore] not effective on virtual properties?

3 Answers3

Linked

Related