XAML ItemsSource and SelectedItem mandatory order of declarations matters, yes?

Question

I observed strange behavior, I have a XAML Combobox (SilverLight4) declaration with SelectedItem and ItemsSource bound, and it seems that the order of SelectedItem and ItemsSource matters ... If SelectedItem is second, the control is not initialized properly (nothing is selected). if it was code, I can understand why it matters because you cannot select an element that is not in the combobox element collection, but it is XAML ...

How do I understand correctly that the order of XAML attributes affects the generated order of lines of code? Or is it something wrong with my code?

Answer 1

- : Silverlight XAML, , XAML .