Ok, I get the impression that most prefer option 2, i.e. keeping Iesi.Collection but in a heavily upgraded version.
Personally I too favor option 2 because it feels cleaner to keep simple collections which don't really have anything to do with NHibernate someplace else. Potentially it could also be interesting for someone else. As an alternative I looked at C5 and PowerCollections, but they both seem to lack a set that preserves insertion order. The latter also isn't updated for .Net 4 ISet. The primary classes of Iesi.Collections 4.0 would be generic OrderedSet, ReadOnlySet and SynchronizedSet. The latter two wraps another set. ReadOnlySet was formerly ImmutableSet, renamed to match .Net BCL naming scheme. I also plan to remove all the non-generic collections. I'll try to push the code during the weekend. /Oskar 2012/10/10 Gerke Geurts <[email protected]> > I agree. The existing BCL interfaces should be enough for NHibernate to > work with. As set ordering is dependent on the database, there should be no > need for NHibernate clients to be aware of the set implementation used to > maintain the order of the loaded data.
