http://blogs.msdn.com/b/dsimmons/archive/2010/07/12/entityroots-an-ef-extensibility-exercise.aspxA little while back I was working on a project for one of the other teams in the Data and Modeling Group where we were building an EDM which was not huge but nevertheless had a number of entity sets, and I was trying various strategies to make the modelen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/dsimmons/archive/2010/07/12/entityroots-an-ef-extensibility-exercise.aspx#10037766Tue, 13 Jul 2010 20:35:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:10037766Daniel Simmons - MSFT<p>Mostly this approach is just a bit quicker and easier than setting up a full repository. &nbsp;Certainly building a full repository gives you greater separation and more control, and for some projects that&#39;s the approach I would take. &nbsp;In other cases, though, it might be that I just want to provide some hints to a consumer of the model (like when I remove a navigation property from one direction on a relationship because I want to help a consumer of the model understand that you usually want to navigate the other way).</p> <p>- Danny</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10037766" width="1" height="1">http://blogs.msdn.com/b/dsimmons/archive/2010/07/12/entityroots-an-ef-extensibility-exercise.aspx#10037605Tue, 13 Jul 2010 12:06:32 GMT91d46819-8472-40ad-a661-2c78acb4018c:10037605JasonBSteele<p>Many thanks for this. Do you think this approach has advantages over using a Repository pattern to hide the Context and therefore &#39;child&#39; Entities?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10037605" width="1" height="1">