Valuemember/Displaymember vs. Delegates

[cody]

I do not think it is good style to use these because you have to hardcode
the propertynamed in your code as string literals. Wouldn't it be better to
use delegates instead?

myComboBox.Disp layMember = new ReturnStringDel egate(myObj.Nam e);
myComboBox.Valu emember = new ReturnObjectDel egate(myObj.Val ue);

[Jakob Christensen]

This would not work as the delegate refers to a property on a specific
object. This is not what you want since you want to call the same property
on a collection of objects.

Regards, Jakob.

"cody" wrote:

I do not think it is good style to use these because you have to hardcode
the propertynamed in your code as string literals. Wouldn't it be better to
use delegates instead?

myComboBox.Disp layMember = new ReturnStringDel egate(myObj.Nam e);
myComboBox.Valu emember = new ReturnObjectDel egate(myObj.Val ue);

[cody]

Damn you are right. There should be some sort of static delegates which
define a method to call but not the object on which to call it.

"Jakob Christensen" <jc*@REMOVEpens ion.dk> schrieb im Newsbeitrag
news:73******** *************** ***********@mic rosoft.com...

This would not work as the delegate refers to a property on a specific
object. This is not what you want since you want to call the same property on a collection of objects.

Regards, Jakob.

"cody" wrote:

I do not think it is good style to use these because you have to hardcode the propertynamed in your code as string literals. Wouldn't it be better to use delegates instead?

myComboBox.Disp layMember = new ReturnStringDel egate(myObj.Nam e);
myComboBox.Valu emember = new ReturnObjectDel egate(myObj.Val ue);

[Jakob Christensen]

Actually, this is what the types System.Componen tModel.Property Descriptor and
System.Reflecti on.PropertyInfo are capable of. But the only way to get a
hold of an instance of PropertyInfo for a property is to use Type.GetPropert y
and the name of the property, which is exactly what ComboBox does (the base
class ListControl does this through the System.Windows. Forms.PropertyM anager
class, I believe).

Regards, Jakob.
"cody" wrote:

Damn you are right. There should be some sort of static delegates which
define a method to call but not the object on which to call it.

"Jakob Christensen" <jc*@REMOVEpens ion.dk> schrieb im Newsbeitrag
news:73******** *************** ***********@mic rosoft.com...

This would not work as the delegate refers to a property on a specific
object. This is not what you want since you want to call the same

property

on a collection of objects.

Regards, Jakob.

"cody" wrote:

I do not think it is good style to use these because you have to hardcode the propertynamed in your code as string literals. Wouldn't it be better to use delegates instead?

myComboBox.Disp layMember = new ReturnStringDel egate(myObj.Nam e);
myComboBox.Valu emember = new ReturnObjectDel egate(myObj.Val ue);