using Generics

[Tony]

Hello!

I just wonder in .NET 2.0 Generics was added.
Before generics existed it was an advantage to get strongly typed methods so
we derived collection classes from CollectionBase
where we had to implement add remove and so on.

But now when generic classes can be used I can't see any point in ever using
this CollectionBase any more.

Do you agree with me?

//Tony

[Jon Skeet [C# MVP]]

On Jun 16, 11:00 am, "Tony" <[e-mail]:

I just wonder in .NET 2.0 Generics was added.
Before generics existed it was an advantage to get strongly typed methods so
we derived collection classes from CollectionBase
where we had to implement add remove and so on.

But now when generic classes can be used I can't see any point in ever using
this CollectionBase any more.

Do you agree with me?

There's little reason to use the nongeneric CollectionBase. However,
there are additional reasons to use something *like* CollectionBase
(and I can't remember the generic equivalent right now) - if you want
to be able to validate items as they are added, hook up events etc.

Jon

[Marc Gravell]

However,

there are additional reasons to use something *like* CollectionBase
(and I can't remember the generic equivalent right now)

Probably System.Collections.ObjectModel.Collection<T>

Unlike List<T>, this has virtual methods as extension points.

Marc

[Jon Skeet [C# MVP]]

On Jun 16, 12:20 pm, Marc Gravell <[e-mail]:

However,
there are additional reasons to use something *like* CollectionBase
(and I can't remember the generic equivalent right now)

Probably System.Collections.ObjectModel.Collection<T>

Unlike List<T>, this has virtual methods as extension points.

Yup, that's the one :)

Jon