What does ValueMember property of ListBox class return?

Question

0.00/5 (No votes)

See more:

.NET

ListBox

programming

, +

Hi!

Can somebody please explain to me what the ValueMember property of the ListBox class does?

Thanks in advance!

Posted 17-Jan-11 12:17pm

Seyed Hamed Khatami

Updated 17-Jan-11 12:46pm

Manfred Rudolf Bihy

v3

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Manfred Rudolf Bihy · Answer 1 · 2011-01-17T12:41:00

Solution 1

A ListBox has display strings those are the ones you see in the GUI and associated with each of these display strings is a value. So the DisplayMember of ListControl gives you the string as you see it in your GUI and the ValueMember property of ListControl (ListBox is derived from ListControl) gives you the associated value.

Please see the example on this site: http://msdn.microsoft.com/en-us/library/system.windows.forms.listcontrol.valuemember.aspx[^]
The example is on the ListControl class site, but it contains an example using the ListBox class.

Hope that helps you!

Best regards,
Manfred

Posted 17-Jan-11 12:41pm

Manfred Rudolf Bihy

Updated 17-Jan-11 12:45pm

v2

Comments

Sergey Alexandrovich Kryukov 17-Jan-11 19:16pm

Good answer (my 5), but Microsoft explanation seems to be more clear than yours.
It should be noted, this thing is invented to provide some binding flexibility based on Reflection.

In my opinion, this is yet another example of Microsoft's technological abuse usual in WinForm library: you see, the ValueMember is of type string, but supposed to be one of member names. If anyone create a string constant for this purpose and misprints it, the compiler is unable to issue a warning and this problem.

Manfred Rudolf Bihy 17-Jan-11 19:20pm

I totally agree with you, if they would have had anything useful in mind they should have made the value part of type object, but hey I'm no Microsoft engineer so what do I know! :)

Sergey Alexandrovich Kryukov 17-Jan-11 19:23pm

I know. All we can do it to prefer one ways of doing thing and be careful with others -- sometimes it helps to save some part of developer's life.