all groups > visual studio .net general > september 2005 >
You're in the

visual studio .net general

group:

Cannot copy assembly 'LIB' to file '\bin\EBX.dll'. The process cannot access the file because it is being used by another process.



Cannot copy assembly 'LIB' to file '\bin\EBX.dll'. The process cannot access the file because it is being used by another process. tascienu NO[at]SPAM ecoaches.com
9/12/2005 6:02:27 PM
visual studio .net general: Symptoms:

1. Create a class library: LIB project in directory c:\LIB
2. Create a WINAPP project in directory c:\WINAPP
3. Include LIB's .dll in WINAPP as a vb.net reference.
4. Build WINAPP. works great.
5. Build LIB. works great.
6. Make changes to LIB.
7. Debug WINAPP with breakpoints.
8. Finish debugging WINAPP.
9. Make changes to LIB.
10. Build lib.
11. Try to make changes to WINAPP. and build it. Error message comes
up:

Cannot copy assembly 'LIB' to file 'c:\WINAPP\bin\EBX.dll'. The
process cannot access the file because it is being used by another
process.

12. Close WINAPP solution. Keep LIB solution open. Re-open WINAPP.
build WINAPP. it works!!!

My question is, which file is being used by another process??? which
one? c:\LIB\BIN\lib.dll or c:\WINAPP\bin\EBX.dll. why when i close the
solution and I open the WINAPP solution again, LIB still unchanged, it
works? how can it be blocking itself from accessing the file??? I would
understand if it is LIB that is blocking it... but i think it blocks
itself...
RE: Cannot copy assembly 'LIB' to file '\bin\EBX.dll'. The process ca Jie
9/13/2005 4:08:03 AM
I experience this problem from time to time to my knowledge it is a
outstanding bug in vs.net.

Jie

[quoted text, click to view]
AddThis Social Bookmark Button