As @Chris says, any of the first three things should work and as @Phyxx says, it doesn’t always really work. The problem is some subtle thing about the order of property changes. To work around it you need to let the WPF invoke your tab-selection code in its own time: Dispatcher.BeginInvoke((Action)(() => MyTabControl.SelectedIndex = x)); … Read more
The TabControl.SelectionChanged is the same event as a ComboBox.SelectionChanged It originates from Selector.SelectionChanged. So, if you do not mark your event as handled in your event handler, it will bubble up the tree, and eventually arrive at your TabControl, which is causing this “firing too often” issue. Mark your event as handled in your SelectionChanged … Read more
This isn’t MVVM. You should not be creating UI elements in your view model. You should be binding the ItemsSource of the Tab to your ObservableCollection, and that should hold models with information about the tabs that should be created. Here are the VM and the model which represents a tab page: public sealed class … Read more