Home/ Questions/Q 152989
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T09:43:17+00:00

Data binding is all about declarative code, right? So I specify what I want

  • 0

Data binding is all about declarative code, right? So I specify what I want with attributes, and the framework takes care of the rest. Unless I’m mistaken and data binding relates to S&M, right?

So, why does the DropDownList control only provide binding fields for its data source, i.e. its list source, and not for its actual data field. i.e. how the heck to I bind the selected value my name DropDownList to the Name field in my Person record? Is this a gross oversight on Microsoft’s part, or on mine?

What is the point of two way data binding if I still have to manually set and read the selected value?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. You might want to do something like the code below. You can not set the ‘SelectedValue’ declaratively, but by saying ‘SelectedValue=<%# [code here] %> you are effectively causing the value to be set when the control is data bound.

    <asp:DropDownList                 ID='DropDownInfoSource'                 runat='server'                 DataSourceID='_employeeDataSource'                 DataTextField='EmployeeName'                 DataValueField='EmployeeID'                 SelectedValue='<%# Bind('EmployeeID') %>'                 />
    • 0