>One can always avoid it. I, personaly, think that if it comes to the point to think on :: the base method is overloaded.

Isn't that the problem Kevin has.

He has defined a container with code in MouseEnter event. He binds to that event but needs to run the code as is. If a developer overloads the Container.MouseEnter the Textbox.Mouseenter of the textbox in his container is overloaded too, although that may not be wanted. But not unless he can bind to / call the code on his class level.

Besides that, I'd recommend the control with an inner container and the textbox inside that. Makes one onion skin more, but keeps the developer away from overloading, what shouldn't be overloadable. The programmer using that class can write code to control.mouseenter still the container and textbox.mouseenter run independantly of that.

Bye, Olaf.