Comments on: Strongly typed Collections of Abstract Objects

By: Kevin Fairclough

Kevin Fairclough — Thu, 20 Nov 2008 15:08:36 +0000

Looking forward to the post on the reasons for dumping CSLA! As we haven’t started our project yet!!

By: Chad Myers

Chad Myers — Wed, 19 Nov 2008 21:04:23 +0000

@Ryan:

If there is some reason you need some functionality on IList that isn’t on IEnumerable+LINQ, then go head, but make it a read-only IList or a copy list so that people aren’t mucking around with your list structure (adding/removing items, etc).

Though I would argue that, most likely, you won’t need IList functionality unless there is some 3rd party grid component or something that requires it.

If the worst comes, you could always to .ToArray() or ToList() on the enumerable.

By: Ryan Kelley

Ryan Kelley — Wed, 19 Nov 2008 19:56:27 +0000

@Frank yes, you can get me on twitter as ryankelley

By: Frank Mao

Frank Mao — Wed, 19 Nov 2008 18:58:44 +0000

I’m glad to hear the reason you are leaving from CLSA. Thanks.
BTW, do you twitter?

By: Ryan Kelley

Ryan Kelley — Wed, 19 Nov 2008 13:51:51 +0000

Chad,

Is an IEnumerable what I really want to use? It just seems so useless. I mean you can iterate the collection but that is it. Part of this is just my ignorance I know, because I am used to large list classes that do everything under the sun.

Also, is it okay for the protected IList to really be an “internal” ilist for mapping purposes?

By: Chad Myers

Chad Myers — Wed, 19 Nov 2008 06:21:56 +0000

Consider not having your IList exposed to the world. This is generally going to lead to other pains (besides the one you have demonstrated here).

In your case, consider having a protected IList and managing what goes in and comes out through public implementations on the individual derived classes.

I.e. IEnumerable GetOrderParts() on the “CustomOrder” class, and also void AddPartToOrder(CustomPart part, int quantity), etc.

-c