Debuggers are hanging in the intestine, but often without any apparent reason it often turns out and gets cured. is.
I'm using the 2010 Microsoft Visual Studio 2010 Professional 10.0.3031 9.1 RTMRL, running a 4.0 client app on a Vista 64 OS.
Cheers, Beryl
/ P>
Good, it happens at all times in 2005 and 2008, generally it is a (A) a public symbols server (yes thread thread I / O UI thread!), Or (b) intellisense , Or (C) what to do with loading symbols (or OS component you are debugging the network stack) and Visual Studio is trying to use it (and the deadlock of things). If (B), wait before waiting for it to begin debugging, it sits in front of you, but in the long run you save time and frustration.
Comments
Post a Comment