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 / Windows Forms / WinForm General / August 2005

Tip: Looking for answers? Try searching our database.

inherited forms - random debugging errors

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Eickhel - 31 May 2005 23:57 GMT
Hey,

I have an application that has many inherited forms from a base form.
Everything works well but every now and then when I hit "Start" VS .Net 2003
gives me errors from the inherited forms.... I need to Rebuild the Solution
and then everything is ok... does anyone knows why does this happen?

Thanks!
AMercer - 01 Jun 2005 00:28 GMT
I have the same problem with a fairly large vb app with about 30 classes.  
Classes are independant of each other except one case of a base class and
four derived classes.  I F5 (start) only after trivial edits.  I rebuild
after extensive edits or any change that affects classes in a major way, eg
changing a method from private to public.  I think MS wants an example before
acknowledging a problem, but examples of this problem require a sufficient
degree of project complexity.  In my opinion, there is a bug in build with
projects of sufficient complexity.

> Hey,
>
[quoted text clipped - 4 lines]
>
> Thanks!
CodeMonkeyGBGB - 29 Aug 2005 15:11 GMT
I have this problem as well.  Is there any solution to this?  It is starting
to drive me nuts.

I make a simple change to the code and all of a sudden, 5 or 6 completly
different forms have "lost" variables or methods.  Most of these forms
inherit from a base form.  Changing the form class on each page from Public
to Private, and back to public ( exactly back to the way it was ) fixes the
problem.

Things I have noticed:
Seems to happen more when I have a designer open, or when a dataset is open.
But, has happend when I have only had code open.
I close all designers before building.
A restart of VS, or the machine usually helps for a while, but it will
always show up.
Did not get really bad until other modules were added and project got large.
Once it does start, and I dont restart, I can almost count on VS quitting
with no warning.  Just disappears.

> I have the same problem with a fairly large vb app with about 30 classes.  
> Classes are independant of each other except one case of a base class and
[quoted text clipped - 13 lines]
> >
> > Thanks!

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.