Re: Problem while debugging

From: ?scar Martins (subdueme_at_hotmail.com)
Date: 08/19/04 

Date: 19 Aug 2004 11:45:35 -0700

I'm using VS.NET 2003 vrs 7.1.3008.
I must say that if I don't have any breakpoint the app behaves
normal(not always). Just when I put a breakpoint it assumes always
that described behaviour...

In my application I have a project with a main form and 2 forms with
one panel each... I also have a module (startup) which has declared
the 3 forms as public. This module instanciates and runs the main
form... This main form as a sector(panel) which itīs filled with a
default panel... When I press a toolbar button the main form removes
the default panel and adds the sector(panel) the respective
panel(instanciating the form if 1rst time added). So far I have just 2
panels as mentioned above. Then, Some events make the panels be
removed and added as the user interacts...
I think the behaviour of the app may be caused by this kind of
"floating panels" that are all publics (the forms) and which one
accesses the database everytime with its own private DB access
object.... Or no??
I'm thinking about to reinstall the VS.net because I can't debug the
app and trace the objects behaviour and its values....

I'm stuck..
Thanks

"One Handed Man \( OHM - Terry Burns \)" <news.microsoft.com> wrote in message news:<#cgYhJdhEHA.3548@TK2MSFTNGP09.phx.gbl>...
> More than likley its bad code, what version are u using ?
>
> --
>
> OHM ( Terry Burns )
> . . . One-Handed-Man . . .
> If U Need My Email ,Ask Me
>
> Time flies when you don't know what you're doing
>
> "?scar Martins" <subdueme@hotmail.com> wrote in message
> news:229f0a23.0408190128.25a08600@posting.google.com...
> > Hi
> >
> > When I'm debugging and somewhere in the code I have a breakpoint, many
> > times when the code after breakpoint finishes and the app returns I
> > can do nothing within in it(it's like freeze)... The app behaves
> > strangely and not accepts any event even close event!!!!! It just
> > lefts for me to stop debugging clicking the respective button in the
> > vs.net toolbar... I don't know if this behaviour is a bug of vs.net or
> > if it's consequence of bad code ... But if would be bad code I think
> > it should stop with any kind of error...
> > Did anybody experienced something like this??
> >
> > Thanks in advance