Skip to content
This repository has been archived by the owner on Apr 23, 2020. It is now read-only.

Unable to copy ... because it is being used by another process. #26

Open
ckincincy opened this issue Jan 14, 2013 · 8 comments
Open

Unable to copy ... because it is being used by another process. #26

ckincincy opened this issue Jan 14, 2013 · 8 comments

Comments

@ckincincy
Copy link

I typically debug using Attach to Process. So the website I am coding on is always running on my machine.

When I build the website for the first time, no issues. However after I do a function that results in Pechkin to be utilized I can't build again.

I get this error on the second build:
Unable to copy file ".... wkkthmltox0.dll" to bin\wkhtmltox0.dll". The process cannot access the file '\bin\wkhtmltox0.dll' because it is being used by another process.

I get that same error for all dlls installed via the NUGET package.

The only way I can build the application again is to manually kill the w3wp.exe process.

Any thoughts?

@gmanny
Copy link
Owner

gmanny commented Feb 4, 2013

I think, as @Kons said in #12 (comment)

the web server process doesn't shut down and the native libraries aren't unloaded

I'm not familiar with web development with .net, so I can't really propose any fix to it.

@stirrblig
Copy link

Just right click the DLL's in the solution explorer and select Properties.
By default, Copy To Output Directory is set to 'Copy Always'.
Change this to 'Copy If Newer' and you're fine.

@mattki
Copy link

mattki commented Mar 7, 2013

Thanks stirrblig, that worked for me in visual studio 2012

@humanbeinc
Copy link

Not working for me ( VS 2010 / Development Server )

@ckincincy
Copy link
Author

Then you did something not quite right as that completely prevents the error. Not possible to reproduce if you don't copy the dll.

@humanbeinc
Copy link

Sry, wrong thread. Wanted to post to the "hanging" in iis thread..

@aloksharma1
Copy link

if you have used nuget package to download simple cut paste to folder it will be their permanently(in VS 2010)

@tuespetre
Copy link

This problem should be resolved in my pull request here: #42

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants