Why should I replace CollectionBase with Generics?

Question

I'm not looking for how, I'm looking for why? I couldn't find a straight forward answer to this.

Answer 1

Yes. CollectionBase was a previous attempt, and a way to provide type safety.

Generics give you these advantages, but add two more HUGE advantages:

1. With generics, you no longer have boxing and unboxing at every access to your collection. This provides a huge perf. advantage.
2. With generics, you can use a single implementation for all of your types. With CollectionBase, each type required a custom implementation, which leads to a huge amount of duplicated code (ie: potential for bugs).

Edit:

I thought of a couple of other compelling reasons to move your code to using generic collections:

1. Using generic collections will allow you to directly use LINQ to Objects on your collections, without requiring calls to Cast<T> (CollectionBase does not implement IEnumerable<T>, only IEnumerable).
2. Provide consistency with any new code, which should always be done using the new generic collections.

Answer 2

Strongly typed access to all the different kinds of collections at the cost of only typing <type>?

EDIT: If you are removing existing and working code, the only reason would be for performance as mentioned elsewhere.