File used by another process...?

[Pankaj]

Hi All:
Is there a solution to below problem...without....restarting VS.Net 2003 so
may be sometimes restarting PC.
//
Cannot copy assembly 'MyClient.Client' to file
'C:\bin\Debug\MyClient.Client.dll'. The process cannot access the file
because it is being used by another process.

-Pankaj

[Pankaj]

Hi Fergus:

Yeah I understand that the dll is being used by other process.. but how do
you find out which process...?
Task Manager doesn't hint a thing about that
I tried to use ListDLLS from sysinternals.com but that doesn't help too ?
What do you use to figure it out ?
I have heard from more than one people...that VS.NET is sometimes using
this...file.
In this post also people have pointed that out.
I wonder like James did ..is this a Bug in VS.NET ?

-Pankaj
"Fergus Cooney" <wo****@tesco.net> wrote in message
news:uD**************@tk2msftngp13.phx.gbl...

Hi Panjak,

I've had the same error. In all cases, for me, it was due to a process
remaining in memory when all visual indications (ie forms, tray icons, etc) had gone. Sometimes my form would terminate but the process remain.
Sometimes it would be a component that was still running free. Depends what I'm developing at the time.

Make friends with Task Manager. If your problem's cause is the same,
TM's got a great Kill switch!! :-)

Regards,
Fergus

[Pankaj]

James:

I would remember to close explorer next time it occurs.... but my gut
feeling is that VS.Net uses this file and it seems like a bug to me
wonder...if MS has to say something about it ?

-Pankaj
"James Liu" <ro*****@sina.com> wrote in message
news:eW**************@TK2MSFTNGP09.phx.gbl...

This is because some other application or process is using MyClent. Even
windows explore can sometimes cause this problem .

You can try to close other application. or check in TaskManager if any
process are using this assembly.

Ironically, sometimes VS.NET is using the assembly. :-) and you have to
restart the VS or even PC.
Is this a bug in VS? or ... when you do developing, anything can happen. It is annoying, anyway, it is a good time to take a cup of coffee.

:-)

James

"Pankaj" <pa******@hotmail.com> дÈëÓʼþ
news:%2***************@TK2MSFTNGP10.phx.gbl...

Hi All:
Is there a solution to below problem...without....restarting VS.Net 2003

so

may be sometimes restarting PC.
//
Cannot copy assembly 'MyClient.Client' to file
'C:\bin\Debug\MyClient.Client.dll'. The process cannot access the file
because it is being used by another process.

-Pankaj

[Daniel O'Connell]

There was a bug that would sometimes lock assemblies. The suspected cause
was assembly size. While i don't know if it was ever proven, when i had the
problem breaking the offending assembly up into 3 pieces (some code
remaining in itself, other pieces being split into other assemblies, it
forced me to modularlize abit more).
It also could have had to do with intellisense or the toolbox(i really don't
remember).
Also, as i recall but don't have any records to be sure, this bug was not
able to be fixed by vs.net 2003 rtm.

Some people ended up switching to a build system using nant, others split up
offending assemblies until they stopped causing trouble,

"Pankaj" <pa******@hotmail.com> wrote in message
news:eH*************@TK2MSFTNGP09.phx.gbl...

Hi Fergus:

Yeah I understand that the dll is being used by other process.. but how do
you find out which process...?
Task Manager doesn't hint a thing about that
I tried to use ListDLLS from sysinternals.com but that doesn't help too ?
What do you use to figure it out ?
I have heard from more than one people...that VS.NET is sometimes using
this...file.
In this post also people have pointed that out.
I wonder like James did ..is this a Bug in VS.NET ?

-Pankaj
"Fergus Cooney" <wo****@tesco.net> wrote in message
news:uD**************@tk2msftngp13.phx.gbl...

Hi Panjak,

I've had the same error. In all cases, for me, it was due to a process remaining in memory when all visual indications (ie forms, tray icons,

etc)

had gone. Sometimes my form would terminate but the process remain.
Sometimes it would be a component that was still running free. Depends

what

I'm developing at the time.

Make friends with Task Manager. If your problem's cause is the same,
TM's got a great Kill switch!! :-)

Regards,
Fergus