I'm using a tool that generates a NHibernate-mappingfile, and all classes I need, based upon a database. The tool gives me a choise to implement collection-properties as IList or as typed collection. e.g. a property Orders can look like this :
public IList Orders {...}

or

public OrdersCollection Orders {...}

In the latter case, the tool also constructs the OrdersCollection-class.
Now what should I use ? Since I'm lazy=true, I prefer the IList. I tried to find what are the best practices, but didn't find anything. Any suggestions ?

Actually, Sergey has just made the new documentation available.
It's well worth a read.

For instance, in section 6.1 (Persisent Collections) it says:



Consult the sticky announcement at the top of the topic list
in the NHibernate forum to find the documentation.

HTH

Sven

If you use internal accessors then they can be IList and you can use a strongly typed collection for your public properties if you want to limit the type of data that the object consumer can add to the collection.

Originally I created a whole bunch of strongly typed collections (which were more than a bit of pain) and then I moved to .NET 2.0. Once I did that I grabbed Ayende's Generics assembly (http://www.ayende.com/projects/nhiberna ... erics.aspx) and used generic collections.

This solution worked really well for me.

Symon.