GUI and Debug Tools

[maurices5000]

this is my sad, sad story.

When i break while debuging in .NET, i'm a newbie coming from vb6, i notice that my form is as white as paper. I can't see anything unless i call a msbox. From what i understand there may not be anythign i could do about this. but how do i test my GUI. IF somethign is poping up on the screen for no known reason, how to i find teh code that makes it appear if my form is white until the event is completely executed?

In VB.old, i could step thru my code, use watch windows, immediate windows, etc and see what is going on. Now i can't see teh GUI. If i don't know how a tool works, what makes the code appear in teh label, i can't use it. ALL code may NOT be obvious, my activeX control could be crypted with a "flash" method, and it may not be obvious to me that this is how the user displays the message on his control. To me this type of trial an error is like sticking your hand in a hole trying to fish out somethign you need, but can't see. I could cost you a lot of hours where the problem is right in your face but you don't see it OR you are no where near it but can't tell how far away you are.

I'm very dismayed if there is nothing i can do about this. i feel very handicapped because much of learning is being able to see exactly what is going on as it happens. There have been many times i've stepped thru code watching the GUI and not figuring it out, but with time and narrowing it down i got it. but just looking at TEXT! No way! It may never click because i can't see where, when or why it is doing it. I may think it is one thing when it may be another.

Thanks guys.

[maurices5000]

Hello, is there anything i can do about this?