Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

C# Entity Framework Basics Extending Our Entity Data Model Adding a One-to-Many Entity Relationship

Posted by Gavin Johnston
Gavin Johnston
9,107 Points

Why do you use a constructor in the principle with one-to-many relationships?

As title says, I have used one-to-many relationships in the past and this consists of simply using navigation properties on one or both classes and it seems to work just fine, but in the video the lecturer goes further and uses a constructor to create a list - why?

1 Answer

Steven Parker
Steven Parker
231,275 Points
Steven Parker
Steven Parker
231,275 Points

Just declaring the collection doesn't populate it, but adding this to the constructor insures that it gets populated when an instance is created. You might not need to do this if your code never accesses the individual items from the series.