How Visual studio differentiates between controls and components

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ramesh - 16 Nov 2005 22:03 GMT

I like to know how VS.NET differentiates controls from components ?. How does
it know when to add a control/component to designer surface or component try ?
Any response is appreciated

Thanks,
Rammy

Reply to this Message

Carlos J. Quintero [VB MVP] - 18 Nov 2005 09:55 GMT

Hi Rammy,

One way to do it is getting the Designer attribute of the component. If it
is a System.Windows.Form.Design.ControlDesigner class (System.Design
assembly), which derives from ComponentDesigner, it is a control. Otherwise
it is a component.

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

>I like to know how VS.NET differentiates controls from components ?. How
>does
[quoted text clipped - 4 lines]
> Thanks,
> Rammy

Reply to this Message

Ramesh - 29 Nov 2005 20:37 GMT

Thank you for your reply. I would like to know if Visual Studio does the same
thing.

> Hi Rammy,
>
[quoted text clipped - 11 lines]
> > Thanks,
> > Rammy

Reply to this Message

Carlos J. Quintero [VB MVP] - 30 Nov 2005 08:57 GMT

Yes, it does, for example in the Document Outline feature of VS 2005.

Signature

> Thank you for your reply. I would like to know if Visual Studio does the
> same
> thing.

Reply to this Message

Rate this thread: