Cannot Copy Assembly <MyAssembly> The Process Cannot Access The File Because It Is Being Used By Another Process

[Ram]

Hey,
I have a solution that is built from both C# and VB.Net projects that some
C# projects are referenced to VB.Net projects and vise versa.
Whenever I try to rebuild my solution I get the following errors:
"Cannot Copy Assembly <Assembly> - The Process Cannot Access The File
Because It Is Being Used By Another Process".
I tried to "kill" the ASPNET_WP process in a pre-built event and had no
success...
I read in more than a few old threads and a few KB articles (313512,324519)
about VS.Net locking assemblies in prior versions of VS.Net - 2002 and found
no real/working resolution.
I'm using VS.Net 2003 with Framework 1.1, Windows XP Pro, IIS 5.1.
Is there a known issue and hopefully a fix for that annoying VS.Net bug?
Thanks ahead

-- Ram

[Klaus H. Probst]

This problem can happen for several reasons. Sometimes doing a full solution
compile (build) helps, but it's difficult to guess what the real cause is.

--
Klaus H. Probst, MVP
http://www.simulplex.net/
"Ram" <ni***@bezeqint.net> wrote in message
news:Oa**************@tk2msftngp13.phx.gbl...

Hey,
I have a solution that is built from both C# and VB.Net projects that some
C# projects are referenced to VB.Net projects and vise versa.
Whenever I try to rebuild my solution I get the following errors:
"Cannot Copy Assembly <Assembly> - The Process Cannot Access The File
Because It Is Being Used By Another Process".
I tried to "kill" the ASPNET_WP process in a pre-built event and had no
success...
I read in more than a few old threads and a few KB articles (313512,324519) about VS.Net locking assemblies in prior versions of VS.Net - 2002 and found no real/working resolution.
I'm using VS.Net 2003 with Framework 1.1, Windows XP Pro, IIS 5.1.
Is there a known issue and hopefully a fix for that annoying VS.Net bug?
Thanks ahead

-- Ram