StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10164988
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-15T18:49:23.250
FavoriteCount
0
LastActivityDate
2012-04-15T21:35:54.890
LastEditDate
2012-04-15T21:35:54.890
LastEditorUserId
303345
OwnerUserId
303345
ParentId
1036377
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
I had this problem and solved it by adding the Newtonsoft.Json.JsonIgnoreAttribute to the property causing the loop. Obviously, that property won't be serialized. To help with this problem, I typically will have both the foreign reference ID and the foreign class in my entities. I realize this is not intuitive (or super great OO), but it is the way recommended by Julia Lerman in her book Programming Entity Framework: Code First. I've found it helps smooth out several problems with Entity Framework. <pre><code> public class SomeEntity { [JsonIgnore] public ForeignEntity SomeForeignEntity {get;set;} public Guid ForeignEntityId {get;set;} } </code></pre> Update: I forgot to mention I also needed to disable proxies on the DbContext like so: <pre><code>dataContext.Configuration.ProxyCreationEnabled = false; </code></pre> If you are writing the code for a service (which seems likely if you are serializing), then this is probably not a problem, but there are some things you lose when the proxy creation is disabled. See here: <a href="http://www.sellsbrothers.com/posts/Details/12665" rel="nofollow">http://www.sellsbrothers.com/posts/Details/12665</a> for more details. I am using the MS Web Api, so I just disable the the proxy creation when I construct my controller: <pre><code>public class MailingApiController : ApiController { public MailingApiController() { PreventDeepSerialization(); } private static void PreventDeepSerialization() { var dataContext = Injector.Get<IIntertwyneDbContext>(); dataContext.Configuration.ProxyCreationEnabled = false; } .... </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSerialize Entity Framework Object using Json.Net
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USDave Welling
UserOwnerUserId
1. USDave Welling
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.