Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / October 2006

Tip: Looking for answers? Try searching our database.

Component in toolbox, appears and disappears...

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
mikemeamail@net2000.ch - 16 Oct 2006 13:49 GMT
Hi all,

I have a windows forms project, under which i've built several
component classes, e.g. extended controls like combobox, textbox and so
forth...

For me to be able to drag and drop them on a form, i always need to
perform the following actions :

- On the Toolbox Panel, under Components tab, right click then
"Add/Remove items"
- Browse to my assembly... "projectname.exe"
- Pick up the components listed, added after the browse, from the .Net
Framework components tab
- Get them added to the toolbox where i'm then able to perform my drag
an drop action

The problem (if any...) is, sometimes, the components after they get
added, remain under the Toolbox panel for weeks and then disappear for
unknown reason to me, so i need to perform the same operation described
above everytime.

So, could anybody explain why this is happening ? Is it because, when
the component class gets modified, we must readd it again in the
toolbox in order to have the latest version ?

Is there any way to add the component so that it remains persistent in
the toolbox pane, unless we do a remove explicitly ?

Thanks for helping,
Mike
Gaurav Vaish (www.EdujiniOnline.com) - 16 Oct 2006 19:17 GMT
> So, could anybody explain why this is happening ? Is it because, when
> the component class gets modified, we must readd it again in the
> toolbox in order to have the latest version ?

Because as soon as you rebuild the control-assembly, Visual Studio
invalidates the previous controls (file gets deleted and recreated after
compilation).

> Is there any way to add the component so that it remains persistent in
> the toolbox pane, unless we do a remove explicitly ?

Yes. First completely build your assembly and then add the controls in the
toolbox.

Signature

Happy Hacking,
Gaurav Vaish | www.mastergaurav.com
www.edujinionline.com
http://eduzine.edujinionline.com
-----------------------------------------

mikemeamail@net2000.ch - 16 Oct 2006 20:48 GMT
Hi Gaurav,
Thanks for helping.
I've noticed that everytime i make a change to my component, and then
perform a  build action, a new version is listed under the .Net
components tab. Is there not a way to specify that the component gets
replaced instead ?
Furthermore, what do you mean by "completely build your assembly" ?
I mean, when i make a change to the component, i always perform a
rebuild action, and then add it to the toolbox. But sometimes, i have
to redo this action again.

> > So, could anybody explain why this is happening ? Is it because, when
> > the component class gets modified, we must readd it again in the
[quoted text clipped - 16 lines]
> http://eduzine.edujinionline.com
> -----------------------------------------

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.