What is the difference between Hashtable and NameValueCollec tion? Thanks.

[davidw]

I always use NameValueCollec tion. But I read an article says the only
differece between Hashtable and NameValueCollec tion is that
NameValueCollec tion could accept more than one value with same key? I am not
quite understand this. And I think NameValueCollec tion's Set is a nice
method. If I use HashTable, how can I update a item in it? Do I have to
check if it exists, and remove and add it again?
Thanks.

[cody]

with a hashtable you can set an existing value using its indexer:

myTable["mykey"] = newValue;

--
cody

Freeware Tools, Games and Humour
http://www.deutronium.de.vu || http://www.deutronium.tk
"davidw" <da****@affinis ys.com> schrieb im Newsbeitrag
news:eC******** ******@TK2MSFTN GP10.phx.gbl...

I always use NameValueCollec tion. But I read an article says the only
differece between Hashtable and NameValueCollec tion is that
NameValueCollec tion could accept more than one value with same key? I am not quite understand this. And I think NameValueCollec tion's Set is a nice
method. If I use HashTable, how can I update a item in it? Do I have to
check if it exists, and remove and add it again?
Thanks.

[Madhu[C#-MVP]]

Hi,

The difference between Hashtable and NameValueCollec tion are the following,

1) As you have mentioned in your post, the NameValueCollec tion can contain more than one values for a particular key whereas Hashtable can contain only one value for a particular key.
2) The Hashtable collection is much more faster than NameValueCollec tion, since it uses the Hashtable algorithm which is faster for retrieves.

For the other part of your question about how to update an item in the hashtable,
You can use the Item property to update the value of the key. But you have to note that, if the specified key already exists in the Hashtable, the value is replaced; otherwise, a new element is created.

I guess it is good practice to check whether the key exists in the collection using Contains or ContainsKey method before you try to update.

I hope this helps...

Regards,
Madhu

Microsoft C# MVP | MCSD.NET
"davidw" wrote:

I always use NameValueCollec tion. But I read an article says the only
differece between Hashtable and NameValueCollec tion is that
NameValueCollec tion could accept more than one value with same key? I am not
quite understand this. And I think NameValueCollec tion's Set is a nice
method. If I use HashTable, how can I update a item in it? Do I have to
check if it exists, and remove and add it again?
Thanks.

[John Wood]

It's also worth mentioning that a NameValueCollec tion can only contain
strings and has this weird interface where it returns multiple values for
one key as a comma separated string.

"Madhu[C#-MVP]" <Ma*******@disc ussions.microso ft.com> wrote in message
news:2A******** *************** ***********@mic rosoft.com...

Hi,

The difference between Hashtable and NameValueCollec tion are the following,
1) As you have mentioned in your post, the NameValueCollec tion can contain more than one values for a particular key whereas Hashtable can contain only
one value for a particular key. 2) The Hashtable collection is much more faster than NameValueCollec tion, since it uses the Hashtable algorithm which is faster for retrieves.
For the other part of your question about how to update an item in the hashtable, You can use the Item property to update the value of the key. But you have to note that, if the specified key already exists in the Hashtable, the
value is replaced; otherwise, a new element is created.
I guess it is good practice to check whether the key exists in the collection using Contains or ContainsKey method before you try to update.
I hope this helps...

Regards,
Madhu

Microsoft C# MVP | MCSD.NET
"davidw" wrote:

I always use NameValueCollec tion. But I read an article says the only
differece between Hashtable and NameValueCollec tion is that
NameValueCollec tion could accept more than one value with same key? I am not quite understand this. And I think NameValueCollec tion's Set is a nice
method. If I use HashTable, how can I update a item in it? Do I have to
check if it exists, and remove and add it again?
Thanks.

[AlexS]

> You can use the Item property to update the value of the key. But you have
to note that, if the specified key already exists in the > Hashtable, the
value is replaced; otherwise, a new element is created.

This is not exactly true. If capacity of hash table is set, simple item[key]
= will add element only when there is free slot. Otherwise assignment will
be "ignored" and you have to use hashTable.Add method to add new value.

HTH
Alex

[Jon Skeet [C# MVP]]

davidw <da****@affinis ys.com> wrote:

I always use NameValueCollec tion. But I read an article says the only
differece between Hashtable and NameValueCollec tion is that
NameValueCollec tion could accept more than one value with same key? I am not
quite understand this.
Well, it's not quite the only difference. Hashtables can take any
object as the key and value; NameValueCollec tions only work with
strings. Essentially NameValueCollec tion has a list of strings for each
key; a Hashtable only has a single value for each key.
And I think NameValueCollec tion's Set is a nice
method. If I use HashTable, how can I update a item in it? Do I have to
check if it exists, and remove and add it again?

No, you can just do

myHashTable[key] = value;

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

AlexS <sa***********@ SPAMsympaticoPL EASE.ca> wrote:

You can use the Item property to update the value of the key. But you have
to note that, if the specified key already exists in the > Hashtable, the
value is replaced; otherwise, a new element is created.

This is not exactly true. If capacity of hash table is set, simple item[key]
= will add element only when there is free slot. Otherwise assignment will
be "ignored" and you have to use hashTable.Add method to add new value.

Could you give an example of that? It seems unlikely to me. Here's a
sample which suggests otherwise:

using System;
using System.Collecti ons;

class Test
{
static void Main()
{
Hashtable table = new Hashtable(5);

for (int i=0; i < 10000; i++)
{
table[i] = i;
}
Console.WriteLi ne (table.Count);
}
}

--
Jon Skeet - <sk***@pobox.co m>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

[Hin]

capacity will be updated when the load factor of the hashtable is reached.
assignment won't be ignored.

--
Regards,
Hin

"AlexS" <sa***********@ SPAMsympaticoPL EASE.ca> wrote in message
news:u9******** ********@TK2MSF TNGP10.phx.gbl. ..

You can use the Item property to update the value of the key. But you have

to note that, if the specified key already exists in the > Hashtable, the
value is replaced; otherwise, a new element is created.

This is not exactly true. If capacity of hash table is set, simple item[key]
= will add element only when there is free slot. Otherwise assignment will
be "ignored" and you have to use hashTable.Add method to add new value.

HTH
Alex