如何在 .Net Core Web API 中停止自引用循环?

本文介绍了如何在 .Net Core Web API 中停止自引用循环?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我遇到了一些问题，我猜这些问题与使用 .NET Core Web API 和 Entity Framework Core 的自引用有关.当我添加 .Includes 用于某些导航属性时，我的 Web API 开始卡住了.

I'm having some issues which I'm guessing are related to self-referencing using .NET Core Web API and Entity Framework Core. My Web API starting choking when I added .Includes for some navigation properties.

我在较旧的 Web API 中找到了似乎是一个解决方案，但我不知道如何为 .NET Core Web API 实现相同的功能(我仍处于早期学习阶段).

I found what appears to be a solution in the older Web API but I don't know how to implement the same thing for .NET Core Web API (I'm still in the early learning stages).

旧的解决方案是在 Global.asax 的 Application_Start() 中坚持这个:

The older solution was sticking this in the Application_Start() of the Global.asax:

GlobalConfiguration.Configuration.Formatters.JsonFormatter.SerializerSettings.ReferenceLoopHandling = ReferenceLoopHandling.Serialize;

我怀疑这是在 StartUp 的 ConfigureService() 方法中处理的，但我对此知之甚少.

I suspect this is handled in the StartUp's ConfigureService() method but I don't know much beyond there.

或者有更合适的方法来处理这个问题吗?

Or is there a more appropriate way to handle this issue?

推荐答案

好的...我终于找到了一些关于这个的参考资料.解决办法是:

Okay... I finally found some reference material on this. The solution is:

public void ConfigureServices(IServiceCollection services) { ... services.AddMvc() .AddJsonOptions( options => options.SerializerSettings.ReferenceLoopHandling = Newtonsoft.Json.ReferenceLoopHandling.Ignore ); ... }

我从这里