Devenv.exe Hangs on Compile... Why? -- dotnet faqs

dotnet faqs : Devenv.exe Hangs on Compile... Why?

Selden McCabe
8/18/2004 1:26:16 PM

Has anybody experienced this problem?
I have a solution that consists of 6 or 7 projects.
Every so often (2 or 3 times a week) when I click Run, everything builds
seemingly OK, but then, just when I would expect the app to start, nothing
happens, and the task manager shows devenv.exe sitting at 100% cpu, fixed
memory (about 127 Megs), forever. The only way out is to kill it from the
task list.

When this happens, I can usually fix it by deleting the OBJ folder under the
main project. But once in a while, this doesn't work. In those cases, I've
tried deleting ALL the OBJ and BIN folders under all the projects, and
sometimes it still happens.

So far, when I'm totally stuck like that, I delete the entire source tree
and get it again from Source Safe.

What is going on? How can I prevent this?

Thanks,
---Selden

Selden McCabe
10/1/2004 8:24:42 AM

Thanks, Brent,

These are both useful things to know and remember the next time this
sort of thing happens.

In my case, neither of these was the culprit, but I eventually did find
a workaround. I'm not sure why it worked though. Here's what I did:

I created a new, empty solution, and one by one, added all the existing
projects to this new solution.

That was months ago and the problem has not come back.

Oddly, all the other team members are still using that original
solution, and none of them is experiencing this problem!

Hope this is helpful to anyone else if it happens to them.

---Selden

*** Sent via Developersdex http://www.developersdex.com ***

Brent Bordelon
10/1/2004 8:53:47 AM

I had this problem at one point, and looked all over for a solution. I
found this somewhere from MS (I looked for it again before responding, but
could not find it - sorry). At any rate, they listed two possibilities,
both of which I had done. I followed the recommendations of both and the
issue was fixed for me. The two possibilities and their recommended fixes
are as follows:

1. Project A references the output dll of Project B. If this is the case,
Project A should reference the PROJECT, not the output dll.
2. You have changed the build output to a directory other than its default
(bin). Change the build output back to the default

Hope this fixes your problem, but I'm sure there are many other things that
could cause this problem
Brent

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet faqs

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008

home · blog · groups

Questions? Comments? Contact the dn