thanks but still a bit confused .......
do you mean to say that there is no difference between a "Class" and a
"component" except that a component can be dragged and dropped........
in that case why bother creating a component ( implementing Icomponent
interface)when everything we write is objectoriented ...dont you guys think we
are better of writing regular classes and create an instance of that class when
needed (Am I missing something?)
------------------------------------
- create a component for re-usable non-UI objects that you want to be able
to add to the VS.NET toolbox and have visual designers for
- create a class for re-usable non-UI objects that don't need to be
dragged/dropped/designable
thanks
sri
---------------------------------
Do you Yahoo!?
All your favorites on one personal page ? Try My Yahoo!
[Non-text portions of this message have been removed]
------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/dpFolB/TM
--------------------------------------------------------------------~->
| 