"Juan Dent" wrote:

> Hi,
>
> Thanks. No actually I found the culprit. I had in my project's references
> path a network path for a computer that was not on. I guess all the waiting
> was going back and forth the network trying to reach this non-existent
> computer.
> Does this make any sense?
> I deleted the reference and boom: no delays.
>
> I would be interested though in learning a bit of what could be going on
> behind the scenes to explain such a severe increase in debugging timeout.
>
> --
> Thanks in advance,
>
> Juan Dent, M.Sc.
>
>
> "Bryan Phillips" wrote:
>
> > Are you debugging mixed code or using a symbol server?
> >
> > --
> > Bryan Phillips
> > MCSD, MCDBA, MCSE
> > Blog: http://bphillips76.spaces.live.com
> > Web Site: http://www.composablesystems.net
> >
> >
> >
> > "Juan Dent" <juanjr@nospam.nospam> wrote in message
> > news:77257FDB-07B9-47F5-9124-46C897A1A8F4@microsoft.com:
> >
> > > Hi,
> > >
> > > I am experiencing extremely slow debugging compared to running out of
> > > debugger. I have eliminated all breakpoints and yet no changes.
> > > I am debugging a C++ app that links to several DLLs; am also using the
> > > multi-threaded DLL runtime - non debug.
> > >
> > > what factors could be contributing to this slowness?
> > > --
> > > Thanks in advance,
> > >
> > > Juan Dent, M.Sc.
> >