Something wierd is happening witn my current project, If I set breakpoint the debugger gets real slow up to the poing that I have to stop it. This is happening since yesterday and in the same way with any form I try to step in for this project.



I tested other SF projects and debugger since to run fine, so I believe something may have become corrupted with the solution/projects.



Have anybody experince this sort of slowness whilde debugging?



Where should I start looking for clues?



I am a bit lost here and need to be able to get this project to work while debugging soon. I could restore a backup from day before yesterday, but I have done many changes and would like to see if whatever is causing the debugger to get slow can be fix without me having to restore a whole backup of the solution and projects.



Thanks.

Edhy Rijo

Edhy,



I'm assuming you've already tried closing and restarting VS, done reboots all the "normal" stuff. If you haven't yet, you also might try doing a clean/rebuild of the solution. Maybe the solution/project files are corrupted, but not likely (they are just XML MS Build files). More likely is that something is whacked with a debug file and a clean "should" remove them, so you can start fresh. This might not work, but it might get you going again.

Thanks Greg,



I have tried all those, since the problem started yesterday, and it does not happen with other projects I tested today. I even tried setting breakpoints in different classes to see if the problem was caused by specific form class or something else.



I google the problem and found this post http://social.msdn.microsoft.com/Forums/en-US/netfxcompact/thread/45c03ca4-cb86-4be4-95dd-2b0b62241413 by Raffaele Limosani, here is the quote:







I disabled that property and now the debug speed seams normal, of course I can not see the values of properties in the code file by hovering the mouse, but I can see them in the "Watch" window. Not a final solution, but at least I can continue working on this project until I found a better solution. I do believe something may be corrupt in this project, but I have not idea where or what to look for.

Edhy Rijo

I wasn't real hopeful that my suggestion would help, but it was an easy thing to try, just in case you hadn't already. I'll be interested if Trent (or some other guru) has some more wisdom on this issue.