SetBounds not virtual in the first place, so if you need to run additional code when boundaries are set, your only options are to override SetBoundsCore .
SetBounds does some parameter checking and contains logic regarding the call to SetBoundsCore with the correct size based on the BoundsSpecified parameter. Furthermore, it should not be called SetBoundsCore , if the size is virtually unchanged.
In other words, SetBoundsCore is the meat of implementation, and SetBounds is a public entry point that contains validation and other housekeeping logic.
driis source share