I have a VB.NET solution setup with 3 projects. 2 are forms Projects the
other is a control/class library project. All were upgraded/imported from VS
2003 Solution. When step into debugging using F8 the IDE seems fine for a
few lines of code and then slows to virtually a standstill. The windows task
manager under processes shows "devenv.exe" 98-99% CPU time and the only way
to free it up is to restart VS 2005 . Anyone else having this problem??
"Lee Button" <lbutton@world-trip.com>, the sinewy sponger and
free-and-easy transvestite who likes abusive self-inflicted intercourse
with roadkill, squalled in <OZsg$VXBGHA.3840@TK2MSFTNGP15.phx.gbl>:
> I have a VB.NET solution setup with 3 projects. 2 are forms Projects
> the other is a control/class library project. All were
[quoted text clipped - 3 lines]
> shows "devenv.exe" 98-99% CPU time and the only way to free it up is
> to restart VS 2005 . Anyone else having this problem??
hahaha - the question should be, "Anyone /NOT/ having this problem?"
I have 2.8GHz hyperthreading Xeons, gigabyte upon gigabyte of RAM and a
dedicated, high-speed harddisk just for pagefile use and I sit here for
minutes on end waiting for the IDE to switch from the project properties
page to a simple form. Minutes - more than 3 or 4, less than ten, all the
while watching the usage graphs for four CPUs going absolutely, freaking
insane.
I am not 100% certain that I have found the culprit yet as I am still
testing my assumed work-around, nevertheless...
It seems the IDE and compiler create myriads of files between them and are
either swapping out pages to disk, or are writing files to disk, at a very
rapid rate, despite the amount of RAM available to the IDE. I have a virus
checker that scans files on both disk read and disk write so have disabled
the virus scanner completely. The IDE seems to be much more responsive. I
say seems to be. Only the failure to clag and run like treacle on a cold
day, and the failure to corrupt even more projects than it already has, will
really tell if the presence of the virus scanner is the root cause /in my
case/.
That you imported the project from 2003 would seem to have no bearing on the
problem.
> When step into debugging using F8 the IDE seems fine for a few lines of code and then slows to virtually a standstill.
> The windows task manager under processes shows "devenv.exe" 98-99% CPU time and the only way to free it up is to
> restart VS 2005 . Anyone else having this problem??
Yes i have the same problems. Did you solve it?
I must Exit the IDE and start again.
pauldewouters@gmail.com - 05 Jan 2006 16:12 GMT
i am having the same problem whilst running an SSIS package in VS
Studio 2005
devenv.exe takes up 70-80% of cpu and the rest is DtsDebugHost.exe !
then Visual studio exits with fatal error message.
schneider - 17 Jan 2006 19:35 GMT
I also. Always restart it.
Schneider
> i am having the same problem whilst running an SSIS package in VS
> Studio 2005
> devenv.exe takes up 70-80% of cpu and the rest is DtsDebugHost.exe !
> then Visual studio exits with fatal error message.