"The process cannot access the file because it is being used by another process"

  • Thread starter Thread starter Earth Worm Jim
  • Start date Start date
E

Earth Worm Jim

I am using VS.Net 2003 on Windows 2003 Server (standard edition) and I am
getting "The process cannot access the file because it is being used by
another process" on DLL's in a VS.Net solution.

I have made sure all the dependancies and the build order is correct but the
actually instance of VS.Net (devenv.exe) is LOCKING THE DAM DLL'S IT IS
TRYING TO BUILD. ?????

I have used Process Explorer from sysinternals.com to confirm this.

VS.Net started this last week and is now doing it with 2 of my projects in
my solution??????

Any one got any ideas?????

The solution does contain 2 DLL's that are in the GAC but are not causing
the issue and are not the DLL's getting locked. 1 DLL that is getting locked
has been registered as a COM+ service, but even when this is deleted it
still locks the dam DLL.

I have turned of Index Server as well and this has not help either

Anyone any idea before I throw the ******* machine out the *******
window....


Cheers

Ollie
 
And Yes I do copy all my DLL's to a common folder....

And Yes I realise this probably the problem, but WOW what a problem that is.
Not all of us are writing "Hello World" applications.......
 
What do you mean with:
when this is deleted it still locks the dam DLL.
what process is holding the file locked?

Willy.
 
devenv.exe aka VS.Net is locking a DLL that it is trying to build so it
can't build the solution.
 
Back
Top