TabControlIt does not process controls specifically, in fact it is normal in any case, when the event is Loadto UserControloccur immediately before the control is displayed for the first time. TabPageIt is responsible for displaying the control, so it will only be "loaded" on the first choice.
To overcome this (completely normal) behavior of Windows Forms, you can transfer your initialization code to a separate method and call it when it loads Form, or instead, you can simply put your initialization code in the constructor UserControl. In any case, you can immediately do your initialization.
source
share