Hi.



I have workstation with Win 2000 Pro and VS.NET Enterprise Developer. For 

development and testing I use server with Windows 2000 Server. That means 

that I connect from my workstation to that server with VS.NET and run 

applications from server etc. just like with Visual InterDev. This server 

has .NET Framework, remote debugging, MDAC2.7 and SQL Server 2000 installed



When I develop ASP.NET project in debug mode and compile it, everything 

works fine the first time. But when compiling same project second time, I 

get error "The file <filename> cannot be copied to the run directory." and 

also error for "bin/xxx.dll" and "bin/xxx.pdb" that they cannot be copied 

to the directory because there's another process using them (VS.NET can't 

overwrite "old" dll on server)



I have a program that shows what is locking the dll on server and it shows 

that it's the "aspnet_wp.exe". If I kill worker process OR restart IIS, I 

can do recompile once and after that it begins to complain again that dll 

is in use (cannot delete dll until I rename it). What could be the reason 

for this? I understanded that the "shadow copy" technique should prevent 

dll's from locking.



This behavior doesn't occur if I develop straight to my workstation. I 

tried installing VS.NET on the server, SDK instead of Framework but 

nothing helped. My user account belongs to Debugger Users and VS 

Developers and Administrators (local and network).



If anybody could help, I would be very grateful.



Thank you.



Teemu Keiski

Application Analyst

Mansoft tietotekniikka Oy

Finland