Why SelectedIndexChanged event for DropDownList sometimes did not fired or beware of the same values in VALUE property

[hal]

I dont know if this helps anyone but i've just banged my head for the
past two hours with the problem of a dropdownlist in asp.net which
somwtimes did not fired or when it was auto posted back the value and
text propertie of the control was always the value of the first
listitem in the control althought i've selected entirely different
item (before the autopost).

After trying manual population of the dropdown control (without
databinding), placing the breakpoints on every imaginable place on the
page the answer was...well..simple.

The matter is that i've populated dropdown with DIFFERENT TEXT
properties but each text propertie had THE SAME value (eg. text
property was John, value propertie vas [e-mail],text property was
Mary, value propertie vas [e-mail], etc... )

And .net through its divine wisdom obviously always checks only VALUE
propertie on postback (text AND value propertie should be a better
choice or maybe not?) and because ALL values were the same (for
testing reason) this little annoying behaviour occured.

Have a nice day!
Timothy

[Eliyahu Goldin]

Thanks Timothy, good to know that.

Eliyahu

"hal" <ha***@walla.com> wrote in message
news:10**************************@posting.google.c om...

I dont know if this helps anyone but i've just banged my head for the
past two hours with the problem of a dropdownlist in asp.net which
somwtimes did not fired or when it was auto posted back the value and
text propertie of the control was always the value of the first
listitem in the control althought i've selected entirely different
item (before the autopost).

After trying manual population of the dropdown control (without
databinding), placing the breakpoints on every imaginable place on the
page the answer was...well..simple.

The matter is that i've populated dropdown with DIFFERENT TEXT
properties but each text propertie had THE SAME value (eg. text
property was John, value propertie vas [e-mail],text property was
Mary, value propertie vas [e-mail], etc... )

And .net through its divine wisdom obviously always checks only VALUE
propertie on postback (text AND value propertie should be a better
choice or maybe not?) and because ALL values were the same (for
testing reason) this little annoying behaviour occured.

Have a nice day!
Timothy

[Jeremy Davis]

Although also checking the text of the submitted item could be helpful, it's
also impossible. When a browser submits a form, it submits a set of
(name,value) pairs for each enabled form element for which it has a value.
So, all the server receives for your list is the name of the list (which
asp.net associates with your control) and the "value" of the selected item.
So, there's no way for asp.net to know which "[e-mail]" the user picked.
Unless you've got something very specific in mind, using duplicate "value"
properties for items in a list is a Bad Idea(tm).

"hal" wrote:

I dont know if this helps anyone but i've just banged my head for the
past two hours with the problem of a dropdownlist in asp.net which
somwtimes did not fired or when it was auto posted back the value and
text propertie of the control was always the value of the first
listitem in the control althought i've selected entirely different
item (before the autopost).

After trying manual population of the dropdown control (without
databinding), placing the breakpoints on every imaginable place on the
page the answer was...well..simple.

The matter is that i've populated dropdown with DIFFERENT TEXT
properties but each text propertie had THE SAME value (eg. text
property was John, value propertie vas [e-mail],text property was
Mary, value propertie vas [e-mail], etc... )

And .net through its divine wisdom obviously always checks only VALUE
propertie on postback (text AND value propertie should be a better
choice or maybe not?) and because ALL values were the same (for
testing reason) this little annoying behaviour occured.

Have a nice day!
Timothy