Silverlight 4 ComboBox SelectedValue not working when ItemsSource changed?

Anyway, you should use SelectedItem instead of SelectedValue if the Employee property is an instance of Employee and not an Employee identifier, otherwise don't forget to specifyc SelectedValuePath too I would also use an ObservableCollection and clear it rather than reassigning a new value, (the binding mode in this case does not have to be 2 way).

I mean employee, already fixed. BTW, I'll try to use SelectedItem instead of SelectedValue, hope it work! :) – Anonymous Nov 24 '10 at 8:03 Keep in mind that SelectedItem will probably not work if you reassign EmployeeList to a different list containing different employees.

– vc 74 Nov 24 '10 at 8:06 SelectedItem not work, anyway I never assign EmployeeList to new instance but clear old item and then add new one to List. Unfortunately this doesn't work. – Anonymous Nov 24 '10 at 8:20 Did you try ObservableCollection?

– vc 74 Nov 24 '10 at 8:56 I already used public ObservableCollection in my ViewModel, am I need to use it at other place? – Anonymous Nov 24 '10 at 9:19.

I too have major issues with the Silverlight 4 ComboBox and SelectedValue bindings. Strangely, using SelectedItem for binding works very well, but that isn't always feasible, especially when using domain objects and FK Id type lookups. Have a look at my post over at the CSLA forums - it resolve most timing and binding issues when using selected value.

forums.lhotka.net/forums/p/9786/45971.aspx Hope that helps.

I can solved this problem by solution from Silverlight ComboBox Sample for RIA Services.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.