Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Yet more VS 2003 Woes

OK, so I am really disliking VS 2003.  I plan to purchase a stop watch just to see how much down time I have with stupid IDE hang ups!  My favorites this week:

"Could not copy temporary files to the output directory.
The file 'Maintenance.exe' cannot be copied to the run directory.  The process cannot access the file because it is being used by another process."

All applications are shut down, only the IDE is running.  What fixes this?  Oh, about 10-15 closes and reopens of the IDE, or, going to the bin directories and deleting everything, all dlls, everything.  Then, I can do a Rebuild.  Usually keeps me down for about 10 minutes.  Yeah!

 

 

 

 

6 Comments

  • Try this:


    1. Shut down the IDE


    2. Delete the obj directory for each project in the solution you are trying to build


    3. Open the IDE and retry the build





    This was a problem we had in 2002 (and in 2003) and this procedure fixed it. To make things easier, we have a batch file that wipes the obj directories...





    Hope this helps!

  • Have you made absolutely sure that the process itself has been killed off, and that you don't have some crazy thread on its own running in the background???

  • Yes, I can do a machine restart, smae thing. Don's suggestion, thus far, is working.

  • I've recently experienced this same problem in 2002; however no matter how many times I rebooted and restarted the IDE, deleted the object dir(s) as Don suggested I couldn't get it to work. I was finally able to rebuild the solution only after resetting all of my project references.



    (hope this helps)

  • If you have multiple projects referencing one another, and have incremental versioning (Version in AssemblyInfo = 1.0.*.* or similar), projects may be holding on to outdated versions of assemblies.



    Try setting version = 1.0.0.0 or some static value in any referenced projects, then re-referencing them. This will keep your dependent assemblies from locking them.

  • Have you made absolutely sure that the process itself has been killed off, and that you don't have some crazy thread on its own running in the background???





    Just check in your Task manager whether the window application exe is running after closing your IDE

Comments have been disabled for this content.