I'm trying to decide whether to use Adapter or 2Class for a new project and have one hangup with the adapter model.

Why doesn't the adapter scenario provide typed collections? Having to cast everything when you pull it out of a collection each time seems painful. Is there a reason for this design decision that I just don't understand? Is that what everyone is doing?

Thanks

Typed collections are a limiter on inheriting classes from entity classes. Say you create a new Order class derived from OrderEntity with a new property: OrderTotal. The OrderCollection class still contains OrderEntity instances, not the order class you wrote. So you have to update all references to the order collection to a new collection. Which can be cumbersome. (I ran into this with selfservicing, that's why I decided to make a generic entitycollection class).

What are you guys referring to here by "typed collections"? You can still pass read-only typed lists around, right? Do you mean the entity collections?

I'm very interested in this because I'm going to use remoting on a new project, so I believe I will have to make the leap from self-servicing to Adaptor model.

Yes, typed entity collections, like CustomerCollection, instead of EntityCollection with customers.