IList vs IEnumerable for Collections on Entities

collections ienumerable ilist
pondermatic picture pondermatic · Dec 18, 2008 · Viewed 52.7k times · Source

When I have entities in my domain with lists of things, should they be exposed as ILists or IEnumerables? E.g. Order has a bunch of OrderLines.

Answer

Matt Hamilton picture Matt Hamilton · Dec 18, 2008

IEnumerable<T> represents a series of items that you can iterate over (using foreach, for example), whereas IList<T> is a collection that you can add to or remove from.

Typically you'll want to be able to modify an Order by adding or removing OrderLines to it, so you probably want Order.Lines to be an IList<OrderLine>.

Having said that, there are some framework design decisions you should make. For example, should it be possible to add the same instance of OrderLine to two different orders? Probably not. So given that you'll want to be able to validate whether an OrderLine should be added to the order, you may indeed want to surface the Lines property as only an IEnumerable<OrderLine>, and provide Add(OrderLine) and Remove(OrderLine) methods which can handle that validation.

Related questions

How to check if IEnumerable is null or empty?

I love string.IsNullOrEmpty method. I'd love to have something that would allow the same functionality for IEnumerable. Is there such? Maybe some collection helper class? The reason I am asking is that in if statements the code looks cluttered …

Read More
Recreating a Dictionary from an IEnumerable<KeyValuePair<>>

I have a method that returns an IEnumerable<KeyValuePair<string, ArrayList>>, but some of the callers require the result of the method to be a dictionary. How can I convert the IEnumerable<KeyValuePair<string, …

Read More
filtering a list using LINQ

i have a list of project objects: IEnumerable<Project> projects a Project class as a property called Tags. this is a int[] i have a variable called filteredTags which is also a int[]. So lets say my filtered …

Read More