StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POViewModel many to many relationship
primarykey
Id
9564485
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-03-05T09:43:45.787
FavoriteCount
0
LastActivityDate
2012-03-05T09:52:56.260
LastEditDate
LastEditorUserId
0
OwnerUserId
1143366
ParentId
0
PostTypeId
1
Score
0
ViewCount
444
LastEditorDisplayName
text
Body
For our project, we would like to use ViewModels. So we decided to create ViewModels for every object we can have : So the ViewModel looks like this (GroupVM) : <pre><code>public class GroupVM : EORTCViewModel<Prisma.BO.Group> { public GroupVM(Prisma.BO.Group group) : base(group) { } public string Name { get { return this._Model.Name; } } public string ShortName { get { return this._Model.ShortName; } } public int Id { get { return this._Model.Id; } } [ScriptIgnore] public ICollection<StudyGroupVM> StudyGroups { get { return Prisma.Web.Models.Factories.ViewModelFactory<Prisma.BO.StudyGroup>.ToViewModel<StudyGroupVM>(this._Model.StudyGroups); } } } </code></pre> The StudyVM : <pre><code>public class StudyVM : EORTCViewModel<Prisma.BO.Study> { public StudyVM(Prisma.BO.Study study) : base(study) { } public string Number { get { return this._Model.Number; } } [ScriptIgnore] public ICollection<StudyGroupVM> StudyGroups { get { return Prisma.Web.Models.Factories.ViewModelFactory<Prisma.BO.StudyGroup>.ToViewModel<StudyGroupVM>(this._Model.StudyGroups); } } } </code></pre> and the intermediate object (StudyGroup) : <pre><code>public class StudyGroupVM : EORTCViewModel<Prisma.BO.StudyGroup> { public StudyGroupVM(Prisma.BO.StudyGroup studyGroup) : base(studyGroup) { } public StudyVM Study { get { return Prisma.Web.Models.Factories.ViewModelFactory<Prisma.BO.Study>.ToViewModel<StudyVM>(this._Model.Study); } } public GroupVM Group { get { return Prisma.Web.Models.Factories.ViewModelFactory<Prisma.BO.Group>.ToViewModel<GroupVM>(this._Model.Group); } } } </code></pre> We would like to use a factory that would create ViewModels for every navigation properties. So we wrote a generic ViewModel factory as follow : <pre><code>public static class ViewModelFactory<T> where T : IEORTCObject { public static R ToViewModel<R>(T model) where R : EORTCViewModel<T> { return (R)Activator.CreateInstance(typeof(R), new object[] { model }); } public static ICollection<R> ToViewModel<R>(ICollection<T> models) where R : EORTCViewModel<T> { ICollection<R> viewModels = new List<R>(); foreach (T model in models) { viewModels.Add((R)Activator.CreateInstance(typeof(R), new object[] { model })); } return viewModels; } } </code></pre> The problem is that when we try to access the StudyGroups property from one of the end object of the relation, it creates correctly the object but then want to recreate the same object because it seems it tries to access the getter for the other end of the relation. This cause a StackOverFlowException since it never stops (cycles). Does any of you have any idea how I can solve this issue ?
Tags
<c#><generics><viewmodel>
Title
ViewModel many to many relationship
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USWhoami
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COall I can say is that Activator.CreateInstance is not a good IOC-container!
 singulars
 PostPostId
 POViewModel many to many relationship
 UserUserId
 USCarsten

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.