For Programmers: Free Programming Magazines  


Home > Archive > Visual Studio > May 2004 > VS hangs when debugging









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author VS hangs when debugging
Paul Nichols

2004-05-24, 6:36 am

I wondered if anyone has encountered the behaviour I’m getting when I debug most areas of my ASP/VB.Net application. Our solution contains about 7 projects and is of a reasonable size, the projects are both a mix of asp applications and dll’s.

When I’m debugging and a breakpoint I’ve set is hit I often find I loose control of VS and it hangs for half a minute. When I get control again the variable or line I was about to evaluate can no long be evaluated and when I hover over variables the t
ool tip shows me the declaration rather than the current value!

This is making my development hell so if anyone can help then I would be very grateful

Regards
Paul

Nick

2004-05-24, 7:41 am


Hi Paul,

1. Do you experience the same behavior if you create a new very simple application such as a "Hello World" one?
2. Can you replicate this on more than the current machine of yours?
3. Have you tried to uninstall the IIS?
4. You may also want to re-register the IIS with regiis_aspnet -i

brg
/Nick
----- Paul Nichols wrote: -----

I wondered if anyone has encountered the behaviour I’m getting when I debug most areas of my ASP/VB.Net application. Our solution contains about 7 projects and is of a reasonable size, the projects are both a mix of asp applications and dll’s.

When I’m debugging and a breakpoint I’ve set is hit I often find I loose control of VS and it hangs for half a minute. When I get control again the variable or line I was about to evaluate can no long be evaluated and when I hover over variables
the tool tip shows me the declaration rather than the current value!

This is making my development hell so if anyone can help then I would be very grateful

Regards
Paul

Jared Parsons [MSFT]

2004-05-24, 3:32 pm

Here is the scenario where this typically happens.

When you step through code, the debugger evaluates all of the properties
that are displayed in the locals window. This means that it is actually
calling into your code and displaying the results.

When you get a hang like this it typically means that one of the properties
the debugger is accessing is hitting an infinite loop or is just taking an
incredibly long time to respond. Once the debugger gives up about half a
minute later it stops displaying properties to prevent hanging again.

One solution is to go to Tools -> Options -> Debugging -> General and
uncheck "Allow property evalution in variable windows". This will disable
the evaluation of properties. You can still right click on them and have
them evaluated

--
Jared Parson [MSFT]
jaredpar@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"Paul Nichols" <paul_nichols@ntlworld.com> wrote in message
news:7745B3D2-68D4-4D76-80C9-696E916C820F@microsoft.com...
> I wondered if anyone has encountered the behaviour I'm getting when I

debug most areas of my ASP/VB.Net application. Our solution contains about 7
projects and is of a reasonable size, the projects are both a mix of asp
applications and dll's.
>
> When I'm debugging and a breakpoint I've set is hit I often find I loose

control of VS and it hangs for half a minute. When I get control again the
variable or line I was about to evaluate can no long be evaluated and when I
hover over variables the tool tip shows me the declaration rather than the
current value!
>
> This is making my development hell so if anyone can help then I would be

very grateful
>
> Regards
> Paul
>



Paul Nichols

2004-05-25, 7:49 am

Thank you guys

You were nearly right Jared, it was my watch window, I don't use it loads, but I'm embarrassed to admit that I didn't realise that it remembered your watches even when you've shut down VS.
I had about 20 objects being evaluated each time I hit any break points, plus I hadn't set that option in the debugging properties, so the debugger was timing out.

Life's great again now thanks :)

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com