When Application.DoEvents() is called, the SelectedValueChanged event is fired. Why?
This is happening in the latest version 2016 Q1. This seems wrong to call a change on a refresh. DoEvents does help make the UI more smooth for users. Other dropdowns (including the default VS one doesn't have this behavior either).
I checked in version 2013 Q3, it did not behave like this.
Please let me know if this is a bug or there is a workaround.
To test: in the SelectedValueChanged call a procedure that has Application.DoEvents(). Step through and you'll see it go call SelectedValueChanged after the doevents.