By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,682 Members | 1,062 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,682 IT Pros & Developers. It's quick & easy.

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

P: n/a
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
Nov 15 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
http://support.microsoft.com/default...microsoft.com:
80/support/kb/articles/q313/5/12.ASP&NoWebContent=1

Ollie

"Earth Worm Jim" <sdd> wrote in message
news:OQ*************@tk2msftngp13.phx.gbl...
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

Nov 15 '05 #2

P: n/a
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.......

"Earth Worm Jim" <sdd> wrote in message
news:OQ*************@tk2msftngp13.phx.gbl...
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

Nov 15 '05 #3

P: n/a
What do you mean with:
when this is deleted it still locks the dam DLL.
what process is holding the file locked?

Willy.
"Earth Worm Jim" <sdd> wrote in message
news:OQ*************@tk2msftngp13.phx.gbl...
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

Nov 15 '05 #4

P: n/a
devenv.exe aka VS.Net is locking a DLL that it is trying to build so it
can't build the solution.

"Willy Denoyette [MVP]" <wi*************@pandora.be> wrote in message
news:ek**************@TK2MSFTNGP09.phx.gbl...
What do you mean with:
when this is deleted it still locks the dam DLL.
what process is holding the file locked?

Willy.
"Earth Worm Jim" <sdd> wrote in message
news:OQ*************@tk2msftngp13.phx.gbl...
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


Nov 15 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.