This was initially discussed here: http://forums.asp.net/thread/1456190.aspx.
To reiterate, the SelectedValue and SelectedItem.Text is passed to the server through the ClientState member as a string of the form "{0}:::{1}" where {0} is the value and {1} is the list text. The server-side code makes no effort to split this into its constituent parts before presenting it through the server-side SelectedValue member. Thus, if a Bind() call deposits "18" into the SelectedValue, the binding logic is sure to choke on the "18:::Descriptive Text Of Some Sort" that comes back.
The article referenced above contains a proposed patch to correct the behaivor.
Comments: This ticket was filed for a pre-15.1 version of AJAX Control Toolkit. If this is still an issue in v15.1 or later, please create a new inquiry.
To reiterate, the SelectedValue and SelectedItem.Text is passed to the server through the ClientState member as a string of the form "{0}:::{1}" where {0} is the value and {1} is the list text. The server-side code makes no effort to split this into its constituent parts before presenting it through the server-side SelectedValue member. Thus, if a Bind() call deposits "18" into the SelectedValue, the binding logic is sure to choke on the "18:::Descriptive Text Of Some Sort" that comes back.
The article referenced above contains a proposed patch to correct the behaivor.
Comments: This ticket was filed for a pre-15.1 version of AJAX Control Toolkit. If this is still an issue in v15.1 or later, please create a new inquiry.