Welcome to the Treehouse Community
The Treehouse Community is a meeting place for developers, designers, and programmers of all backgrounds and skill levels to get support. Collaborate here on code errors or bugs that you need feedback on, or asking for an extra set of eyes on your latest project. Join thousands of Treehouse students and alumni in the community today. (Note: Only Treehouse students can comment or ask questions, but non-students are welcome to browse our conversations.)
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and a supportive community. Start your free trial today.
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?
Steven Parker217,469 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.