AS YOU SAW IN CHAPTER 9: Components, it is possible to create specialized classes, known as components, which can be hosted on a form's nonvisual design surface. Components can be configured using Windows Forms Designer features such as the Properties window and generally make lighter work for developers. What components don't do, however, is provide a UI that's painted directly to a region on a container, such as a form or panel, which they are directly responsible for. Also, components cannot directly process user input. The weapon of choice in these situations is the control.
A control is a reusable class that derives from the System.Windows.Forms.Control base implementation (either directly or indirectly) ...