The file 'assembly name' cannot be copied to the run directory. The process cannot access the file because it is being used by another process

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

SevDer - 17 Aug 2005 20:50 GMT

Hi I am having the following problem almost on daily bases.

QUOTE
Could not copy temporary files to the output directory.
The file 'assembly name' cannot be copied to the run directory. The process
cannot access the file because it is being used by another process.
UNQUOTE

I've checked the following article but resolutions over there do not help
me.
http://support.microsoft.com/default.aspx?scid=kb;en-us;313512

I have Win2003 Ent. VSNet2003 with FW1.1 SP1
This mostly happens when I switch between release & debug modes.

As an example, today I switched from yesterdays release mode to debug mode
and one of the projects (base project) throw this problem.
In these cases what I generally do is, move back to other mode(in this case
release mode) and go to the bin&obj folders of the project and delete
problematic mode folders (in todays case debug)

However, even this sometimes does not work. Today it failed also. After I
switched back to release mode, I was able to delete bin/debug folder but
obj/debug. The problematic file in this folder was the assemblyname.dll.

I checked which application was locking this file with WhosLockingIt and it
showed devenv.exe (vsnet) although I was at release mode.

Anyway, workaround is to close, wait 30-60 secs. until file is released,
delete file and open vsnet again.
I hate this procedure.

Is there a fix for this problem?

Signature

SevDer
http://www.sevder.com
A new .NET Source For .NET Developers

Reply to this Message

"Gary Chang[MSFT]" - 18 Aug 2005 08:50 GMT

Hi,

>I've checked the following article but resolutions over there
>do not help me.
>http://support.microsoft.com/default.aspx?scid=kb;en-us;313512

It appears to be a VS.NET IDE's problem, this behavior is by design. If all
the resolutions in the above KB article could not fix your problem, I am
afraid currently there isn't a specific workaround to your case.

In order to repro the problem in our local environment, would you please
upload a small-alone solution(zipped) to me, if it is not inconvenience to
you, maybe we can perform some tests first on my side.
(Please remove the "online" of my email address)

Meanwhile, if you need a solution to work around this problem, it is better
for you if one of our PSS support engineers could work with you. This may
need you submit a support incident in Microsoft PSS (Product Support
Service). As a MSDN subscriber, you have two free support incidents.

By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents.

For your reference, I attached steps to contact Microsoft PSS here: You can
contact Microsoft Product Support directly to discuss additional support
options you may have available, by contacting us at 1-(800)936-5800 or by
choosing one of the options listed at:

http://support.microsoft.com/d-efault.aspx?scid=fh;EN-US;Offe-rProPhone

Thanks for your understanding!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

The file 'assembly name' cannot be copied to the run directory. The process cannot access the file because it is being used by another process

Free Magazines