What is the difference between Component and UserControl?

[Frank Rizzo]

In the WinForms context.

[Ignacio Machin ( .NET/ C# MVP )]

On May 8, 3:47*pm, Frank Rizzo <[e-mail]:

In the WinForms context.

UserControl derive from (like 4 or 5 levels below) Component.

Other than that I see no other relationship

What is the doubt that you have?

[Frank Rizzo]

Ignacio Machin ( .NET/ C# MVP ) wrote:

On May 8, 3:47 pm, Frank Rizzo <[e-mail]:

>In the WinForms context.

UserControl derive from (like 4 or 5 levels below) Component.

Other than that I see no other relationship

What is the doubt that you have?

Just wanted to know how I should start coding my control. It seems that
other than a workable designer UserControl does not offer anything else
over Component.

[Peter Duniho]

On Thu, 08 May 2008 15:17:56 -0700, Frank Rizzo <no**@none.netwrote:

Just wanted to know how I should start coding my control. It seems that
other than a workable designer UserControl does not offer anything else
over Component.

Coding what control?

If you intend to write a custom control for use in a Forms application,
then you should inherit Control, not Component. Not only does that
provides a very large, basic feature set that you'd need to reimplement
anyway, a lot of the Forms API requires Control instances anyway.
Starting with Component just won't do.

UserControl is misnamed. It's really more of a design-time custom
control, used for making new composite controls out of existing controls.
It's definitely not the right general-purpose base class for a custom
control. You'd only use it if your custom control was in fact an
aggregate of several other pre-existing controls. The name sounds
general-purpose, but the control is not.

Pete