Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
5
Newest
 Scholar
Impact
~236 people reached

  • 0 posts edited
  • 0 helpful flags
  • 2 votes cast
Dec
14
awarded  Scholar
Dec
14
accepted Contract / Project / Line-Item hierarchy design considerations
Oct
30
awarded  Autobiographer
Jan
23
awarded  Popular Question
Oct
26
comment Contract / Project / Line-Item hierarchy design considerations
@GlenH7 The circular references do cause me some pain though because we're using the DataContractSerializer (saving to XML as well as sending to a WCF service). I know we can use an attribute to mark an object as containing a reference, but this gets ugly quickly working up the object hierarchy. I was just curious if there was a cleaner way of doing things. I suppose I don't really need a "Parent" property on the Model...I can handle communication back to the parent via events.
Oct
25
comment Contract / Project / Line-Item hierarchy design considerations
Thanks for your response. I'll review your thoughts above. Do you have any recommendations for eliminating the circular references from the tree structure? That is, how can a child project know it's parent without directly having a reference to it's parent object?
Oct
25
awarded  Supporter
Oct
25
awarded  Student
Oct
25
asked Contract / Project / Line-Item hierarchy design considerations