I have noticed that VS.NET sometimes locks assemblies after building
them. I have had problems where a build fails because the assembly could
not be deleted (as in a clean operation). I don't see this problem if
I'm using the command line (i.e. devenv.com). Don't know that this
VS.NET behavior is r
> Is this a "feature" of the so-called MS .Net XCopy deploy functionality?
Is
> there anything that I can do to ensure that the delete and copy will
> actually work, as this error is not really making life easy for a
hands-off
> build and deploy
It can be some anti-virus software doing their job.
Well,
ASP.Net is actually supposed to make copies of the DLL's in the bin
folder and use the copies. It does this to facilitate XCOPY deployment
and live updates. I'm not sure why you are having the problem.
Are you ALWAYS able to copy them using the command line? Have you tried
to use the shel
