Silly me, I don't know why I had in back of my mind that it didn't! Excuse me for invalid question!
On 1/22/08, Mark Hurd <[EMAIL PROTECTED]> wrote: > > Yes it does. > > (If the question was why didn't I use it: it was because I already had > inherited from Dictionary`2 for other purposes, so I was really just > dumbing down the inherited collection.) > > Regards, > Mark Hurd, B.Sc.(Ma.)(Hons.) > > On 22/01/2008, Miika Makinen <[EMAIL PROTECTED]> wrote: > > Ah, Namevaluecollection allows duplicate keys? > > > > On 1/22/08, Mark Hurd <[EMAIL PROTECTED]> wrote: > > > > > > I wrote a lot of code working with Dictionary`2 for this sort of > > > scenario, then I realised I needed duplicate "Keys", so I built my > > > own NameValueList(Of TName, TValue) inheriting from List(Of > > > KeyValuePair(Of TName, TValue)) > > > > > > Regards, > > > Mark Hurd, B.Sc.(Ma.)(Hons.) > > > > > > On 22/01/2008, Miika Makinen <[EMAIL PROTECTED]> wrote: > > > > Hi guys, > > > > What do you think? Do you think there's a reason to use > > > > namevaluecollection in .Net 2+ application? Does it perform > > > > better? > > > > > > > > Dictionary<string,string> is nice as you can quite easily refactor > > > > later to use some other types as keys or values... > > > > > > > > Miika > > =================================== > This list is hosted by DevelopMentor(R) http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
