5

Was research on how (for convetion) define a Many Many where table where both fields are primary key and found this post.

So decide to install the Iesi.Collections in my library domain.

But there came a doubt. In the "Iesi.Collections" outperforms "System.Collections" Iesi.Collections? Why should I use?

It is better in performance?

9

Iesi.Collections was originally released in 2004, when the .NET Framework was at v1.1. As of .NET 3.5, the .NET Framework includes a HashSet collection type, which provides the Set functionality that Iesi.Collections was intended to address. Unless you have a specific reason to use Iesi.Collections (e.g., NHibernate depends on it), it probably makes sense to use the standard .NET classes instead, since they are more likely to be supported and maintained.

|improve this answer|||||

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.