A quick one: Up until this latest version of the ASP.NET Ajax extensions, one of the glaring “bugs” (if you want to call it that) with the CascadingDropDown control was that it returned the backend value of the dropdown rather than the actual selected display value. This caused problems when trying to access the SelectedValue. The only way to quasi-cleanly work around this was to manually edit the associated javascript.
Well, I just found out that this problem was addressed in the latest release. You can now access the SelectedValue of a CascadingDropDown control without having to implement a messy workaround:
ddlCars.SelectedItem.Text
Not anything ground-breaking, but a very welcome fix.
Listening to Broken Social Scene – You Forgot It in People…
My Nose is In Daniel Quinn – Ishamel…
{ 4 comments… read them below or add one }
I don’t know what you’re talking about. CascadingDropDown controls don’t have a SelectedItem property and accessing the SelectedItem.Text property on the associated DropDownList doesn’t get the most recent selection.
You’re right. The CascadingDropDown control doesn’t have a SelectedItem property, but the associated DropDownList control does. And I have found that the SelectedItem.Text property on the associated DropDownList gets the selected value with ASP.NET AJAX Extensions (at the time that I wrote the article, still “Atlas” RC1) and up. I’ve implemented it, and am using it in several different applications.
Guess we’ll have to agree to disagree.
On what event of control can i set ddlCars.SelectedItem.Text
You can access the SelectedItem.Text value using just about any event that you want, including the on change event. I often use a button click event, but there are numerous ways to do it, obviously depending on what you’re looking to do.