K
Kejpa
Hi,
I've begun trying out the .NET2005 beta and one thing that I was thrilled
about in advance was the CollectionBase class. No more selfmade Collection
classes I thought.
But now I'm puzzled, I can't have a Collection class based on the
CollectionBase that accepts strings as key? It only accepts integers!
Why would I use a CollectionBase class as the base class of my collection if
it can't have a string as it's key?
Why not stick to the old way and have an internal
Collection/Hashtable/ListDictionary/WhatEver as holder for your objects ?
Should I make a suggestion to MS?
Regards
/Kejpa
I've begun trying out the .NET2005 beta and one thing that I was thrilled
about in advance was the CollectionBase class. No more selfmade Collection
classes I thought.
But now I'm puzzled, I can't have a Collection class based on the
CollectionBase that accepts strings as key? It only accepts integers!
Why would I use a CollectionBase class as the base class of my collection if
it can't have a string as it's key?
Why not stick to the old way and have an internal
Collection/Hashtable/ListDictionary/WhatEver as holder for your objects ?
Should I make a suggestion to MS?
Regards
/Kejpa