dotnet windows forms: inherited forms - random debugging errors -- dotnet windows forms

RE: inherited forms - random debugging errors

AMercer
5/31/2005 4:28:38 PM

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.

[quoted text, click to view]

RE: inherited forms - random debugging errors

CodeMonkeyGBGB
8/29/2005 7:11:04 AM

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.

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet windows forms group.