Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 4
    Confirming this issue is still present in .NET 4...best to just rely on SelectedItem instead of SelectedValue Commented Feb 8, 2012 at 17:16
  • 1
    I am currently having issues with SelectedValue in .NET 4.5... For me SelectedItem too solves the issue. Commented Jan 21, 2013 at 23:27
  • 2
    I have a similar issue which seems to be acting oppositely from what your describing , where i am using only SelectedItem stackoverflow.com/questions/22300281/… Commented Mar 10, 2014 at 12:52
  • 3
    This answer solves the issue (SelectedItem actually does what both of these guys seem to have thought SelectedValue was supposed to do), but it's mistaken about the cause of the problem. The problem was that SelectedValue needs SelectedValuePath. This is documented. SelectedValue and SelectedItem do different things. Commented Jun 16, 2016 at 12:56
  • I managed to solve this in my case by adding UpdateSourceTrigger=PropertyChanged to the SelectedValue binding. To me it feels like a special kind of ridiculous that I had to set that value at all. Commented Nov 13, 2017 at 17:00