title: EF Code First - Models , when should properties be instantiated in constructor?
body: <p>I was wondering if there is a good explanation somewhere as to when a Property will need to be instantiated 
  in a model class constructor and when it is not necessary?</p>
  
  <p>Docu on the MS EF site is good and covers a lot of related topics</p>
  
  <p>Relationships and Navigation Properties -  <a href="http://msdn.microsoft.com/en-us/data/jj713564" rel="nofollow">http://msdn.microsoft.com/en-us/data/jj713564</a><br>
  Configuring relationships with API <a href="http://msdn.microsoft.com/en-us/data/jj591620%20%22Configuring%20relationships%20with%20API" rel="nofollow">http://msdn.microsoft.com/en-us/data/jj591620%20%22Configuring%20relationships%20with%20API</a> </p>
  
  <p>Entity Framework class library  <a href="http://msdn.microsoft.com/en-us/library/hh289362%28v=vs.103%29.aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/hh289362%28v=vs.103%29.aspx</a></p>
  
  <p>and im also part way through reading the Book Programming Entity Framework - Code First By  Julia Lerman </p>
  
  <p>I would like to better understand when a property needs to be instantiated in the Model constructor.<br>
  I see Samples in MS documentation and in the Book with and without newed up  properties in the Model constructor.
  There is most likely a good reason why some solutions use a constructor with newed Up objects and others not.<br>
  Seems like <code>Virtual ICollection</code> has the <code>new List&lt;&gt;</code> and complex type has <code>new RefObj</code>.
  But simple <code>virtual navigation property</code> of type ModelObject are Ok without new.</p>
  
  <p><strong>Can I stick to a pattern without knowing the internals of each convention class. Or is there another topic I should be reading?</strong></p>