blocks|key|1197533|text|在我的例子中，问题是我返回了从数据上下文中获得的实体框架对象。解决办法是先分离每个对象，然后再重新处理它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1197534|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, the problem was that I was returning Entity Framework objects that I got from the data context. The solution was to detach each object before retuning them.

blocks|key|2754283|text|在我的例子中，分离对象是不可能的，因为EF上下文已经被释放了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2754284|相反，我使用了AsNotTracking扩展方法。|offset|length|style|CODE|2754285|...On其他一些情况下，我还必须通过将某些导航属性设置为null来削减循环引用。|2754286|...And+DataContract(IsReference+=+true)并没有做到这一点。|2754287|有关此问题的更多详细信息可在此处找到：N层实体框架与WCF问题|2754288|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/gg679352|1|http://msdn.microsoft.com/en-us/library/vstudio/system.runtime.serialization.datacontractattribute.isreference|2|http://www.binaryforge-software.com/wpblog/?p=129^0|0|7|D|7|D|0|0|0|7|W|7|W|1|0|J|C|2|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@$D|13|E|14|1|15]]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@$D|18|E|19|F|G]]|9|@$D|1A|E|1B|1|1C]]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|N|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]|X|$5|Q|R|S|A|$T|Y]]]]

In my case, detaching objects was not possible because the EF context was already disposed.

Instead, I used the <a href="http://msdn.microsoft.com/en-us/library/gg679352" rel="nofollow"><code>AsNotTracking</code></a> extension method.

...On some other cases, I also had to cut circular references by setting some navigation properties to null.

...And <a href="http://msdn.microsoft.com/en-us/library/vstudio/system.runtime.serialization.datacontractattribute.isreference" rel="nofollow"><code>DataContract(IsReference = true)</code></a> did not do the trick.

More details on this issue can be found here : <a href="http://www.binaryforge-software.com/wpblog/?p=129" rel="nofollow">N-tier Entity Framework and debugging WCF problems</a>

blocks|key|2394494|text|应该使用REST启动器工具包不再受支持和ASP.NET网络API或任何其他最新的REST框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2394495|entityMap|0|LINK|mutability|MUTABLE|url|http://aspnet.codeplex.com/wikipage?title=WCF%2520REST|1|http://www.asp.net/web-api^0|4|F|0|K|C|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

<a href="http://aspnet.codeplex.com/wikipage?title=WCF%20REST" rel="nofollow">REST Starter Kit is no longer supported</a> and <a href="http://www.asp.net/web-api" rel="nofollow">ASP.NET Web API</a> or any other up-to-date REST framework should be used instead.

blocks|key|2754372|text|我今天也有同样的问题。如果数据契约中没有正确设置KnowType和IsReference，则这可能是一个循环引用。首先检查这些点。真的!|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2754373|但当你面对这种行为的时候。|2754374|代码有时运行良好，但确实会抛出错误。|2754375|您还应该检查您在线路上发送的图形是否是深而复杂的(就像两个以上的导航属性深度一样)。然后，它可能只是绑定配置中ReaderQuotas的ReaderQuotas，它太低了。当最深的导航属性为空时，您的服务将工作，但当它们包含至少一个元素时，则会抛出此错误。|2754376|此配置的默认值为32，因此尝试使用64。|2754377|现在，我们可以讨论在WCF配置中使用过多的深图而不是使用低默认值的低质量设计。|2754378|我不是说你必须把你的图表分解成更小的部分，但你应该。|2754379|entityMap^0|1L|B|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|Z|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|10|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|11|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|S|$]]

I had the same issue today. It could be a circular reference if you don't have set correctly the KnowType and the IsReference in your data contract. Check those points first. Really !

But when your are facing this kind of behavior.

The code is working fine sometimes but it do throw error.

You should also check if the graph your are sending on the wire is deep and complex (like more than two navigation properties deep). Then it could just be the MaxDepth of the ReaderQuotas in your binding configuration which is too low. Your service would work when your deepest navigations properties are empty but would throw this error when they contains at least one element.

Default value of this configuration is 32, so give a try to 64.

Now we can argue about the poor quality design of using too much deep graph on service versus the low default value in WCF Configuration. 

I'm not saying you have to break your graph in smaller part, but you should.

I have created a REST Service in WCF. I am facing the following issue

<blockquote>
 There was an error deserializing the object of type System.Collections.Generic.IList. The maximum read depth (32) has been exceeded because XML data being read has more levels of nesting than is allowed by the quota. This quota may be increased by changing the MaxDepth property on the XmlDictionaryReaderQuotas object used when creating the XML reader.
</blockquote>

I haven't specified any type of binding in configuration since I have developed the service as per REST Starter Kit. Please suggest something as to how can I fix it.

The code is working fine sometimes but it do throw error.

Error while deserializing the object in WCF

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我在WCF中创建了一个REST服务。我面临以下问题反序列化System.Collections.Generic.IList类型的对象时出错。超过了最大读取深度(32)，因为正在读取的XML数据具有比配额允许的更多的嵌套级别。可以通过更改在创建XML读取器时使用的MaxDepth对象上的XmlDictionaryReaderQuotas属性来增加此配额。我没有在配置中指定任何类型的绑定，因为我已经按

问在WCF中反序列化对象时出错
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在WCF中反序列化对象时出错EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在WCF中反序列化对象时出错
EN