I keep getting the following error every time I compile the solution under
VS 2005:
----------------
Error 5
Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll". The process
cannot access the file 'bin\Debug\xyz.dll' because it is being used by
another process.
----------------
In order to get rid of this problem, I have to constantly close and restart
VS 2005. Is anybody else getting the same problem?
Thanks.
27  1898 
You're getting this error because of just what it says...the dll is in use
by another application. Make sure that you are closing the application that
you've compiled and run last to make sure that the file isn't still being
accessed. Could you also please include the real name of the dll file that
you're access...I'm guessing it's not really xyz.dll...that might help us
figure out what processes might be using the dll...
Chris
--
Securing your systems is much like fighting off disease -- as long as you
maintain basic hygiene, you're likely to be okay, but you'll never be
invulnerable.
Steve Shah - Unix Systems Network Administrator
"Rene" <no****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP14.phx.gbl... I keep getting the following error every time I compile the solution under
VS 2005:
----------------
Error 5
Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll". The
process cannot access the file 'bin\Debug\xyz.dll' because it is being
used by another process.
----------------
In order to get rid of this problem, I have to constantly close and
restart VS 2005. Is anybody else getting the same problem?
Thanks.
I am sure that I am closing the application completely. It is the Visual
Studio IDE itself what is not releasing the file. This is evident because
things go back to normal when I close VS 2005 and reopen it again.
I have been working on this project for around 2 years using VS 2003 and
never had this problem happened until I started using VS 2005.
I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as an
indication that nothing is running but I continue to get this error. Perhaps
there is some other process in the VS 2005 IDE that keeps holding on to the
file after I stop debugging but I have no idea what is that process.
The file name is not "xyz" but is also not a system or VS specific file, is
one of my own. I have even deleted this file hoping that VS would recreate
the file and snap out of the problem but eventually it display the error
message again.
"Chris Springer" <cs*****@adelphia.net> wrote in message
news:IP********************@adelphia.com... You're getting this error because of just what it says...the dll is in use
by another application. Make sure that you are closing the application
that you've compiled and run last to make sure that the file isn't still
being accessed. Could you also please include the real name of the dll
file that you're access...I'm guessing it's not really xyz.dll...that
might help us figure out what processes might be using the dll...
Chris
--
Securing your systems is much like fighting off disease -- as long as you
maintain basic hygiene, you're likely to be okay, but you'll never be
invulnerable.
Steve Shah - Unix Systems Network Administrator
"Rene" <no****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP14.phx.gbl...I keep getting the following error every time I compile the solution under
VS 2005:
----------------
Error 5
Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll". The
process cannot access the file 'bin\Debug\xyz.dll' because it is being
used by another process.
----------------
In order to get rid of this problem, I have to constantly close and
restart VS 2005. Is anybody else getting the same problem?
Thanks.
Rene wrote: I am sure that I am closing the application completely. It is the Visual
Studio IDE itself what is not releasing the file. This is evident because
things go back to normal when I close VS 2005 and reopen it again.
I have been working on this project for around 2 years using VS 2003 and
never had this problem happened until I started using VS 2005.
I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as an
indication that nothing is running but I continue to get this error. Perhaps
there is some other process in the VS 2005 IDE that keeps holding on to the
file after I stop debugging but I have no idea what is that process.
The file name is not "xyz" but is also not a system or VS specific file, is
one of my own. I have even deleted this file hoping that VS would recreate
the file and snap out of the problem but eventually it display the error
message again.
"Chris Springer" <cs*****@adelphia.net> wrote in message
news:IP********************@adelphia.com... You're getting this error because of just what it says...the dll is in use
by another application. Make sure that you are closing the application
that you've compiled and run last to make sure that the file isn't still
being accessed. Could you also please include the real name of the dll
file that you're access...I'm guessing it's not really xyz.dll...that
might help us figure out what processes might be using the dll...
Chris
--
Securing your systems is much like fighting off disease -- as long as you
maintain basic hygiene, you're likely to be okay, but you'll never be
invulnerable.
Steve Shah - Unix Systems Network Administrator
"Rene" <no****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP14.phx.gbl... I keep getting the following error every time I compile the solution under
VS 2005:
----------------
Error 5
Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll". The
process cannot access the file 'bin\Debug\xyz.dll' because it is being
used by another process.
----------------
In order to get rid of this problem, I have to constantly close and
restart VS 2005. Is anybody else getting the same problem?
Thanks.
I sometimes have the same problem on VS 2003. Have to restart VS.
Not sure if that's VS or OS issue...
You may have this problem in VS 2003 if you are using Source Safe, it a
known bug and there is a hot fix for that but this is not supposed to happen
with VS 2005.
"MuZZy" <tn*@newsgroups.nospam> wrote in message
news:uR**************@TK2MSFTNGP10.phx.gbl... Rene wrote: I am sure that I am closing the application completely. It is the Visual
Studio IDE itself what is not releasing the file. This is evident because
things go back to normal when I close VS 2005 and reopen it again.
I have been working on this project for around 2 years using VS 2003 and
never had this problem happened until I started using VS 2005.
I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as an
indication that nothing is running but I continue to get this error.
Perhaps there is some other process in the VS 2005 IDE that keeps holding
on to the file after I stop debugging but I have no idea what is that
process.
The file name is not "xyz" but is also not a system or VS specific file,
is one of my own. I have even deleted this file hoping that VS would
recreate the file and snap out of the problem but eventually it display
the error message again.
"Chris Springer" <cs*****@adelphia.net> wrote in message
news:IP********************@adelphia.com... You're getting this error because of just what it says...the dll is in
use by another application. Make sure that you are closing the
application that you've compiled and run last to make sure that the file
isn't still being accessed. Could you also please include the real name
of the dll file that you're access...I'm guessing it's not really
xyz.dll...that might help us figure out what processes might be using
the dll...
Chris
--
Securing your systems is much like fighting off disease -- as long as
you maintain basic hygiene, you're likely to be okay, but you'll never
be invulnerable.
Steve Shah - Unix Systems Network Administrator
"Rene" <no****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP14.phx.gbl...
I keep getting the following error every time I compile the solution
under VS 2005:
----------------
Error 5
Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll". The
process cannot access the file 'bin\Debug\xyz.dll' because it is being
used by another process.
----------------
In order to get rid of this problem, I have to constantly close and
restart VS 2005. Is anybody else getting the same problem?
Thanks.
I sometimes have the same problem on VS 2003. Have to restart VS.
Not sure if that's VS or OS issue...
Rene wrote: I am sure that I am closing the application completely. It is the
Visual Studio IDE itself what is not releasing the file. This is
evident because things go back to normal when I close VS 2005 and
reopen it again.
I have been working on this project for around 2 years using VS 2003
and never had this problem happened until I started using VS 2005.
I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as
an indication that nothing is running but I continue to get this
error. Perhaps there is some other process in the VS 2005 IDE that
keeps holding on to the file after I stop debugging but I have no
idea what is that process.
The file name is not "xyz" but is also not a system or VS specific
file, is one of my own. I have even deleted this file hoping that VS
would recreate the file and snap out of the problem but eventually it
display the error message again.
If it's a multi-project solution as in the following:
- project A
- project B, references A
- project C, references B
- project D, references C, A
be sure to only set copy-local to true for A in the reference to A in
D.
FB
--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
MuZZy wrote: Rene wrote: I am sure that I am closing the application completely. It is the
Visual Studio IDE itself what is not releasing the file. This is
evident because things go back to normal when I close VS 2005 and
reopen it again.
I have been working on this project for around 2 years using VS
2003 and never had this problem happened until I started using VS
2005.
I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled
as an indication that nothing is running but I continue to get this
error. Perhaps there is some other process in the VS 2005 IDE that
keeps holding on to the file after I stop debugging but I have no
idea what is that process.
The file name is not "xyz" but is also not a system or VS specific
file, is one of my own. I have even deleted this file hoping that
VS would recreate the file and snap out of the problem but
eventually it display the error message again.
"Chris Springer" <cs*****@adelphia.net> wrote in message
news:IP********************@adelphia.com... You're getting this error because of just what it says...the dll is in use >> by another application. Make sure that you are closing
the application >> that you've compiled and run last to make sure
that the file isn't still >> being accessed. Could you also please
include the real name of the dll >> file that you're access...I'm
guessing it's not really xyz.dll...that >> might help us figure out
what processes might be using the dll...
Chris
--
Securing your systems is much like fighting off disease -- as long as you >> maintain basic hygiene, you're likely to be okay, but
you'll never be >> invulnerable.
Steve Shah - Unix Systems Network Administrator
"Rene" <no****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP14.phx.gbl...
I keep getting the following error every time I compile the solution under >>> VS 2005: >
----------------
Error 5
>
Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll". The >>> process cannot access the file 'bin\Debug\xyz.dll' because it
is being >>> used by another process. ----------------
>
>
In order to get rid of this problem, I have to constantly close and >>> restart VS 2005. Is anybody else getting the same problem? >
Thanks.
>
I sometimes have the same problem on VS 2003. Have to restart VS.
Not sure if that's VS or OS issue...
VS issue. Call PSS and ask for fix with KB number 887818.
FB
--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
Rene wrote: I am sure that I am closing the application completely. It is the
Visual Studio IDE itself what is not releasing the file. This is
evident because things go back to normal when I close VS 2005 and
reopen it again.
I have been working on this project for around 2 years using VS 2003
and never had this problem happened until I started using VS 2005.
I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as
an indication that nothing is running but I continue to get this
error. Perhaps there is some other process in the VS 2005 IDE that
keeps holding on to the file after I stop debugging but I have no
idea what is that process.
The file name is not "xyz" but is also not a system or VS specific
file, is one of my own. I have even deleted this file hoping that VS
would recreate the file and snap out of the problem but eventually it
display the error message again.
Also, a virusscanner can lock the file or windows' Indexing service.
Be sure both aren't looking in your bin folders. This happens because
as soon as the file is written, these services get a signal and get
into gear, grab the file and vs.net can't reference it right after that
when it compiles a project referencing that dll just written.
FB
"Chris Springer" <cs*****@adelphia.net> wrote in message
news:IP********************@adelphia.com... You're getting this error because of just what it says...the dll is
in use by another application. Make sure that you are closing the
application that you've compiled and run last to make sure that the
file isn't still being accessed. Could you also please include the
real name of the dll file that you're access...I'm guessing it's
not really xyz.dll...that might help us figure out what processes
might be using the dll...
Chris
--
Securing your systems is much like fighting off disease -- as long
as you maintain basic hygiene, you're likely to be okay, but you'll
never be invulnerable.
Steve Shah - Unix Systems Network Administrator
"Rene" <no****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP14.phx.gbl... I keep getting the following error every time I compile the
solution under VS 2005:
----------------
Error 5
Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll". The >> process cannot access the file 'bin\Debug\xyz.dll' because it
is being >> used by another process. ----------------
In order to get rid of this problem, I have to constantly close
and >> restart VS 2005. Is anybody else getting the same problem?
--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
Has anyone found a solution to this problem?
Frans Bouma [C# MVP] wrote: Rene wrote:
I am sure that I am closing the application completely. It is the
Visual Studio IDE itself what is not releasing the file. This is
evident because things go back to normal when I close VS 2005 and
reopen it again.
I have been working on this project for around 2 years using VS 2003
and never had this problem happened until I started using VS 2005.
I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as
an indication that nothing is running but I continue to get this
error. Perhaps there is some other process in the VS 2005 IDE that
keeps holding on to the file after I stop debugging but I have no
idea what is that process.
The file name is not "xyz" but is also not a system or VS specific
file, is one of my own. I have even deleted this file hoping that VS
would recreate the file and snap out of the problem but eventually it
display the error message again.
Also, a virusscanner can lock the file or windows' Indexing service.
Be sure both aren't looking in your bin folders. This happens because
as soon as the file is written, these services get a signal and get
into gear, grab the file and vs.net can't reference it right after that
when it compiles a project referencing that dll just written.
FB
"Chris Springer" <cs*****@adelphia.net> wrote in message
news:IP********************@adelphia.com... You're getting this error because of just what it says...the dll is
in use by another application. Make sure that you are closing the
application that you've compiled and run last to make sure that the
file isn't still being accessed. Could you also please include the
real name of the dll file that you're access...I'm guessing it's
not really xyz.dll...that might help us figure out what processes
might be using the dll...
Chris
--
Securing your systems is much like fighting off disease -- as long
as you maintain basic hygiene, you're likely to be okay, but you'll
never be invulnerable.
Steve Shah - Unix Systems Network Administrator
"Rene" <no****@nospam.com> wrote in message
news:OH**************@TK2MSFTNGP14.phx.gbl...
> I keep getting the following error every time I compile the
> solution under VS 2005:
>
> ----------------
> Error 5
>
> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
The >> process cannot access the file 'bin\Debug\xyz.dll' because it
is being >> used by another process.> ----------------
>
>
> In order to get rid of this problem, I have to constantly close
and >> restart VS 2005. Is anybody else getting the same problem?
--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
> Has anyone found a solution to this problem?
Frans gave you the solution (re-arrange your project references).
As to finding exactly _which_ process has your file locked, I suggest you
use the free utility "unlocker" ( http://ccollomb.free.fr/unlocker/) it will
tell you who has the file locked and allow you to forcibly remove the file
lock. VS might not like it very much, but it's worth a try.
> Frans gave you the solution (re-arrange your project references).
That did not work.
"Gabriel Magaña" <no*****@no-spam.com> wrote in message
news:e0**************@TK2MSFTNGP10.phx.gbl... Has anyone found a solution to this problem?
Frans gave you the solution (re-arrange your project references).
As to finding exactly _which_ process has your file locked, I suggest you
use the free utility "unlocker" (http://ccollomb.free.fr/unlocker/) it
will tell you who has the file locked and allow you to forcibly remove the
file lock. VS might not like it very much, but it's worth a try.
I am currently working with a Microsoft engineer trying to solve this
problem. It's been around 2 weeks and they are still trying to find what is
the cause of this problem is. They are currently escalating the issue
because the problem does not seem to have a straight answer.
Do you have a project that has the problem that you would be willing to give
to the Microsoft engineer? If you do, let me know so I can put you in touch
with the engineer and he can try to reproduce the problem in his PC and try
to narrow down the problem.
Thanks.
"The ants are driving me crazy" <cw******@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com... Has anyone found a solution to this problem?
Frans Bouma [C# MVP] wrote: Rene wrote:
> I am sure that I am closing the application completely. It is the
> Visual Studio IDE itself what is not releasing the file. This is
> evident because things go back to normal when I close VS 2005 and
> reopen it again.
>
> I have been working on this project for around 2 years using VS 2003
> and never had this problem happened until I started using VS 2005.
>
> I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as
> an indication that nothing is running but I continue to get this
> error. Perhaps there is some other process in the VS 2005 IDE that
> keeps holding on to the file after I stop debugging but I have no
> idea what is that process.
>
> The file name is not "xyz" but is also not a system or VS specific
> file, is one of my own. I have even deleted this file hoping that VS
> would recreate the file and snap out of the problem but eventually it
> display the error message again.
Also, a virusscanner can lock the file or windows' Indexing service.
Be sure both aren't looking in your bin folders. This happens because
as soon as the file is written, these services get a signal and get
into gear, grab the file and vs.net can't reference it right after that
when it compiles a project referencing that dll just written.
FB
>
>
>
> "Chris Springer" <cs*****@adelphia.net> wrote in message
> news:IP********************@adelphia.com...
> > You're getting this error because of just what it says...the dll is
> > in use by another application. Make sure that you are closing the
> > application that you've compiled and run last to make sure that the
> > file isn't still being accessed. Could you also please include the
> > real name of the dll file that you're access...I'm guessing it's
> > not really xyz.dll...that might help us figure out what processes
> > might be using the dll...
> >
> > Chris
> >
> > --
> > Securing your systems is much like fighting off disease -- as long
> > as you maintain basic hygiene, you're likely to be okay, but you'll
> > never be invulnerable.
> >
> > Steve Shah - Unix Systems Network Administrator
> > "Rene" <no****@nospam.com> wrote in message
> > news:OH**************@TK2MSFTNGP14.phx.gbl...
> > > I keep getting the following error every time I compile the
> > > solution under VS 2005:
> > >
> >> ----------------
> >> Error 5
> > >
> >> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
> The >> process cannot access the file 'bin\Debug\xyz.dll' because it
> is being >> used by another process.
> >> ----------------
> > >
> > >
> >> In order to get rid of this problem, I have to constantly close
> and >> restart VS 2005. Is anybody else getting the same problem?
--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
I am getting the same errors. Rearranging the projects might fix it but
that does not explain why the compile will work some times and not others.
If the order of the projects is invalid it shoud fail everytime, correct?
I also tried the unlocker with no success. Does anyone have an answer on
how to get around this?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... I am currently working with a Microsoft engineer trying to solve this
problem. It's been around 2 weeks and they are still trying to find what is
the cause of this problem is. They are currently escalating the issue
because the problem does not seem to have a straight answer.
Do you have a project that has the problem that you would be willing to
give to the Microsoft engineer? If you do, let me know so I can put you in
touch with the engineer and he can try to reproduce the problem in his PC
and try to narrow down the problem.
Thanks.
"The ants are driving me crazy" <cw******@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com... Has anyone found a solution to this problem?
Frans Bouma [C# MVP] wrote: Rene wrote:
> I am sure that I am closing the application completely. It is the
> Visual Studio IDE itself what is not releasing the file. This is
> evident because things go back to normal when I close VS 2005 and
> reopen it again.
>
> I have been working on this project for around 2 years using VS 2003
> and never had this problem happened until I started using VS 2005.
>
> I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as
> an indication that nothing is running but I continue to get this
> error. Perhaps there is some other process in the VS 2005 IDE that
> keeps holding on to the file after I stop debugging but I have no
> idea what is that process.
>
> The file name is not "xyz" but is also not a system or VS specific
> file, is one of my own. I have even deleted this file hoping that VS
> would recreate the file and snap out of the problem but eventually it
> display the error message again.
Also, a virusscanner can lock the file or windows' Indexing service.
Be sure both aren't looking in your bin folders. This happens because
as soon as the file is written, these services get a signal and get
into gear, grab the file and vs.net can't reference it right after that
when it compiles a project referencing that dll just written.
FB
>
>
>
> "Chris Springer" <cs*****@adelphia.net> wrote in message
> news:IP********************@adelphia.com...
> > You're getting this error because of just what it says...the dll is
> > in use by another application. Make sure that you are closing the
> > application that you've compiled and run last to make sure that the
> > file isn't still being accessed. Could you also please include the
> > real name of the dll file that you're access...I'm guessing it's
> > not really xyz.dll...that might help us figure out what processes
> > might be using the dll...
> >
> > Chris
> >
> > --
> > Securing your systems is much like fighting off disease -- as long
> > as you maintain basic hygiene, you're likely to be okay, but you'll
> > never be invulnerable.
> >
> > Steve Shah - Unix Systems Network Administrator
> > "Rene" <no****@nospam.com> wrote in message
> > news:OH**************@TK2MSFTNGP14.phx.gbl...
> > > I keep getting the following error every time I compile the
> > > solution under VS 2005:
> > >
> >> ----------------
> >> Error 5
> > >
> >> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
> The >> process cannot access the file 'bin\Debug\xyz.dll' because it
> is being >> used by another process.
> >> ----------------
> > >
> > >
> >> In order to get rid of this problem, I have to constantly close
> and >> restart VS 2005. Is anybody else getting the same problem?
--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
Do you have a project with the problem that you would be willing to share
with the Microsoft engineer?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:ev**************@TK2MSFTNGP12.phx.gbl... I am getting the same errors. Rearranging the projects might fix it but
that does not explain why the compile will work some times and not others.
If the order of the projects is invalid it shoud fail everytime, correct?
I also tried the unlocker with no success. Does anyone have an answer on
how to get around this?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...I am currently working with a Microsoft engineer trying to solve this
problem. It's been around 2 weeks and they are still trying to find what
is the cause of this problem is. They are currently escalating the issue
because the problem does not seem to have a straight answer.
Do you have a project that has the problem that you would be willing to
give to the Microsoft engineer? If you do, let me know so I can put you
in touch with the engineer and he can try to reproduce the problem in his
PC and try to narrow down the problem.
Thanks.
"The ants are driving me crazy" <cw******@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com... Has anyone found a solution to this problem?
Frans Bouma [C# MVP] wrote:
Rene wrote:
> I am sure that I am closing the application completely. It is the
> Visual Studio IDE itself what is not releasing the file. This is
> evident because things go back to normal when I close VS 2005 and
> reopen it again.
>
> I have been working on this project for around 2 years using VS 2003
> and never had this problem happened until I started using VS 2005.
>
> I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled as
> an indication that nothing is running but I continue to get this
> error. Perhaps there is some other process in the VS 2005 IDE that
> keeps holding on to the file after I stop debugging but I have no
> idea what is that process.
>
> The file name is not "xyz" but is also not a system or VS specific
> file, is one of my own. I have even deleted this file hoping that VS
> would recreate the file and snap out of the problem but eventually it
> display the error message again.
Also, a virusscanner can lock the file or windows' Indexing service.
Be sure both aren't looking in your bin folders. This happens because
as soon as the file is written, these services get a signal and get
into gear, grab the file and vs.net can't reference it right after that
when it compiles a project referencing that dll just written.
FB
>
>
>
> "Chris Springer" <cs*****@adelphia.net> wrote in message
> news:IP********************@adelphia.com...
> > You're getting this error because of just what it says...the dll is
> > in use by another application. Make sure that you are closing the
> > application that you've compiled and run last to make sure that the
> > file isn't still being accessed. Could you also please include the
> > real name of the dll file that you're access...I'm guessing it's
> > not really xyz.dll...that might help us figure out what processes
> > might be using the dll...
> >
> > Chris
> >
> > --
> > Securing your systems is much like fighting off disease -- as long
> > as you maintain basic hygiene, you're likely to be okay, but you'll
> > never be invulnerable.
> >
> > Steve Shah - Unix Systems Network Administrator
> > "Rene" <no****@nospam.com> wrote in message
> > news:OH**************@TK2MSFTNGP14.phx.gbl...
> > > I keep getting the following error every time I compile the
> > > solution under VS 2005:
> > >
> >> ----------------
> >> Error 5
> > >
> >> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
> The >> process cannot access the file 'bin\Debug\xyz.dll' because it
> is being >> used by another process.
> >> ----------------
> > >
> > >
> >> In order to get rid of this problem, I have to constantly close
> and >> restart VS 2005. Is anybody else getting the same problem?
--
------------------------------------------------------------------------
Get LLBLGen Pro, productive O/R mapping for .NET:
http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------
I will try and create one but, here is what I think is going on.
Our program laods data from a database and one of the tables takes several
seconds so in order to release control back to the user a second thread is
created to load the large table. If the user shuts down the application
before this process is complete the file is locked.
Are you doing anything similiar on your side?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Do you have a project with the problem that you would be willing to share
with the Microsoft engineer?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:ev**************@TK2MSFTNGP12.phx.gbl...I am getting the same errors. Rearranging the projects might fix it but
that does not explain why the compile will work some times and not others.
If the order of the projects is invalid it shoud fail everytime, correct?
I also tried the unlocker with no success. Does anyone have an answer on
how to get around this?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...I am currently working with a Microsoft engineer trying to solve this
problem. It's been around 2 weeks and they are still trying to find what
is the cause of this problem is. They are currently escalating the issue
because the problem does not seem to have a straight answer.
Do you have a project that has the problem that you would be willing to
give to the Microsoft engineer? If you do, let me know so I can put you
in touch with the engineer and he can try to reproduce the problem in
his PC and try to narrow down the problem.
Thanks.
"The ants are driving me crazy" <cw******@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
Has anyone found a solution to this problem?
Frans Bouma [C# MVP] wrote:
> Rene wrote:
>
> > I am sure that I am closing the application completely. It is the
> > Visual Studio IDE itself what is not releasing the file. This is
> > evident because things go back to normal when I close VS 2005 and
> > reopen it again.
> >
> > I have been working on this project for around 2 years using VS 2003
> > and never had this problem happened until I started using VS 2005.
> >
> > I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled
> > as
> > an indication that nothing is running but I continue to get this
> > error. Perhaps there is some other process in the VS 2005 IDE that
> > keeps holding on to the file after I stop debugging but I have no
> > idea what is that process.
> >
> > The file name is not "xyz" but is also not a system or VS specific
> > file, is one of my own. I have even deleted this file hoping that VS
> > would recreate the file and snap out of the problem but eventually
> > it
> > display the error message again.
>
> Also, a virusscanner can lock the file or windows' Indexing service.
> Be sure both aren't looking in your bin folders. This happens because
> as soon as the file is written, these services get a signal and get
> into gear, grab the file and vs.net can't reference it right after
> that
> when it compiles a project referencing that dll just written.
>
> FB
>
> >
> >
> >
> > "Chris Springer" <cs*****@adelphia.net> wrote in message
> > news:IP********************@adelphia.com...
> > > You're getting this error because of just what it says...the dll
> > > is
> > > in use by another application. Make sure that you are closing the
> > > application that you've compiled and run last to make sure that
> > > the
> > > file isn't still being accessed. Could you also please include
> > > the
> > > real name of the dll file that you're access...I'm guessing it's
> > > not really xyz.dll...that might help us figure out what processes
> > > might be using the dll...
> > >
> > > Chris
> > >
> > > --
> > > Securing your systems is much like fighting off disease -- as long
> > > as you maintain basic hygiene, you're likely to be okay, but
> > > you'll
> > > never be invulnerable.
> > >
> > > Steve Shah - Unix Systems Network Administrator
> > > "Rene" <no****@nospam.com> wrote in message
> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
> > > > I keep getting the following error every time I compile the
> > > > solution under VS 2005:
> > > >
> > >> ----------------
> > >> Error 5
> > > >
> > >> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
> > The >> process cannot access the file 'bin\Debug\xyz.dll' because it
> > is being >> used by another process.
> > >> ----------------
> > > >
> > > >
> > >> In order to get rid of this problem, I have to constantly close
> > and >> restart VS 2005. Is anybody else getting the same problem?
>
>
> --
> ------------------------------------------------------------------------
> Get LLBLGen Pro, productive O/R mapping for .NET:
> http://www.llblgen.com
> My .NET blog: http://weblogs.asp.net/fbouma
> Microsoft MVP (C#)
> ------------------------------------------------------------------------
I don't have to go that far, I don't even have to run the program, in order
for me to get the error all I have to do is rename a project file or rename
some variable on the offending project and I will get the error when
compiling for the second time.
Do you only get the error when after running the program? Can you try to
lock the file simply recompiling the program and not run it?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:u5*************@TK2MSFTNGP15.phx.gbl... I will try and create one but, here is what I think is going on.
Our program laods data from a database and one of the tables takes several
seconds so in order to release control back to the user a second thread is
created to load the large table. If the user shuts down the application
before this process is complete the file is locked.
Are you doing anything similiar on your side?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Do you have a project with the problem that you would be willing to share
with the Microsoft engineer?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:ev**************@TK2MSFTNGP12.phx.gbl...I am getting the same errors. Rearranging the projects might fix it but
that does not explain why the compile will work some times and not
others. If the order of the projects is invalid it shoud fail everytime,
correct?
I also tried the unlocker with no success. Does anyone have an answer
on how to get around this?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
I am currently working with a Microsoft engineer trying to solve this
problem. It's been around 2 weeks and they are still trying to find what
is the cause of this problem is. They are currently escalating the issue
because the problem does not seem to have a straight answer.
Do you have a project that has the problem that you would be willing to
give to the Microsoft engineer? If you do, let me know so I can put you
in touch with the engineer and he can try to reproduce the problem in
his PC and try to narrow down the problem.
Thanks.
"The ants are driving me crazy" <cw******@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
> Has anyone found a solution to this problem?
>
>
> Frans Bouma [C# MVP] wrote:
>> Rene wrote:
>>
>> > I am sure that I am closing the application completely. It is the
>> > Visual Studio IDE itself what is not releasing the file. This is
>> > evident because things go back to normal when I close VS 2005 and
>> > reopen it again.
>> >
>> > I have been working on this project for around 2 years using VS
>> > 2003
>> > and never had this problem happened until I started using VS 2005.
>> >
>> > I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled
>> > as
>> > an indication that nothing is running but I continue to get this
>> > error. Perhaps there is some other process in the VS 2005 IDE that
>> > keeps holding on to the file after I stop debugging but I have no
>> > idea what is that process.
>> >
>> > The file name is not "xyz" but is also not a system or VS specific
>> > file, is one of my own. I have even deleted this file hoping that
>> > VS
>> > would recreate the file and snap out of the problem but eventually
>> > it
>> > display the error message again.
>>
>> Also, a virusscanner can lock the file or windows' Indexing service.
>> Be sure both aren't looking in your bin folders. This happens because
>> as soon as the file is written, these services get a signal and get
>> into gear, grab the file and vs.net can't reference it right after
>> that
>> when it compiles a project referencing that dll just written.
>>
>> FB
>>
>> >
>> >
>> >
>> > "Chris Springer" <cs*****@adelphia.net> wrote in message
>> > news:IP********************@adelphia.com...
>> > > You're getting this error because of just what it says...the dll
>> > > is
>> > > in use by another application. Make sure that you are closing
>> > > the
>> > > application that you've compiled and run last to make sure that
>> > > the
>> > > file isn't still being accessed. Could you also please include
>> > > the
>> > > real name of the dll file that you're access...I'm guessing it's
>> > > not really xyz.dll...that might help us figure out what processes
>> > > might be using the dll...
>> > >
>> > > Chris
>> > >
>> > > --
>> > > Securing your systems is much like fighting off disease -- as
>> > > long
>> > > as you maintain basic hygiene, you're likely to be okay, but
>> > > you'll
>> > > never be invulnerable.
>> > >
>> > > Steve Shah - Unix Systems Network Administrator
>> > > "Rene" <no****@nospam.com> wrote in message
>> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
>> > > > I keep getting the following error every time I compile the
>> > > > solution under VS 2005:
>> > > >
>> > >> ----------------
>> > >> Error 5
>> > > >
>> > >> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
>> > The >> process cannot access the file 'bin\Debug\xyz.dll' because
>> > it
>> > is being >> used by another process.
>> > >> ----------------
>> > > >
>> > > >
>> > >> In order to get rid of this problem, I have to constantly close
>> > and >> restart VS 2005. Is anybody else getting the same problem?
>>
>>
>> --
>> ------------------------------------------------------------------------
>> Get LLBLGen Pro, productive O/R mapping for .NET:
>> http://www.llblgen.com
>> My .NET blog: http://weblogs.asp.net/fbouma
>> Microsoft MVP (C#)
>> ------------------------------------------------------------------------
>
I could never pin point the problem. Were you ever able to resolve this
issue?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Do you have a project with the problem that you would be willing to share
with the Microsoft engineer?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:ev**************@TK2MSFTNGP12.phx.gbl...I am getting the same errors. Rearranging the projects might fix it but
that does not explain why the compile will work some times and not others.
If the order of the projects is invalid it shoud fail everytime, correct?
I also tried the unlocker with no success. Does anyone have an answer on
how to get around this?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...I am currently working with a Microsoft engineer trying to solve this
problem. It's been around 2 weeks and they are still trying to find what
is the cause of this problem is. They are currently escalating the issue
because the problem does not seem to have a straight answer.
Do you have a project that has the problem that you would be willing to
give to the Microsoft engineer? If you do, let me know so I can put you
in touch with the engineer and he can try to reproduce the problem in
his PC and try to narrow down the problem.
Thanks.
"The ants are driving me crazy" <cw******@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
Has anyone found a solution to this problem?
Frans Bouma [C# MVP] wrote:
> Rene wrote:
>
> > I am sure that I am closing the application completely. It is the
> > Visual Studio IDE itself what is not releasing the file. This is
> > evident because things go back to normal when I close VS 2005 and
> > reopen it again.
> >
> > I have been working on this project for around 2 years using VS 2003
> > and never had this problem happened until I started using VS 2005.
> >
> > I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled
> > as
> > an indication that nothing is running but I continue to get this
> > error. Perhaps there is some other process in the VS 2005 IDE that
> > keeps holding on to the file after I stop debugging but I have no
> > idea what is that process.
> >
> > The file name is not "xyz" but is also not a system or VS specific
> > file, is one of my own. I have even deleted this file hoping that VS
> > would recreate the file and snap out of the problem but eventually
> > it
> > display the error message again.
>
> Also, a virusscanner can lock the file or windows' Indexing service.
> Be sure both aren't looking in your bin folders. This happens because
> as soon as the file is written, these services get a signal and get
> into gear, grab the file and vs.net can't reference it right after
> that
> when it compiles a project referencing that dll just written.
>
> FB
>
> >
> >
> >
> > "Chris Springer" <cs*****@adelphia.net> wrote in message
> > news:IP********************@adelphia.com...
> > > You're getting this error because of just what it says...the dll
> > > is
> > > in use by another application. Make sure that you are closing the
> > > application that you've compiled and run last to make sure that
> > > the
> > > file isn't still being accessed. Could you also please include
> > > the
> > > real name of the dll file that you're access...I'm guessing it's
> > > not really xyz.dll...that might help us figure out what processes
> > > might be using the dll...
> > >
> > > Chris
> > >
> > > --
> > > Securing your systems is much like fighting off disease -- as long
> > > as you maintain basic hygiene, you're likely to be okay, but
> > > you'll
> > > never be invulnerable.
> > >
> > > Steve Shah - Unix Systems Network Administrator
> > > "Rene" <no****@nospam.com> wrote in message
> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
> > > > I keep getting the following error every time I compile the
> > > > solution under VS 2005:
> > > >
> > >> ----------------
> > >> Error 5
> > > >
> > >> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
> > The >> process cannot access the file 'bin\Debug\xyz.dll' because it
> > is being >> used by another process.
> > >> ----------------
> > > >
> > > >
> > >> In order to get rid of this problem, I have to constantly close
> > and >> restart VS 2005. Is anybody else getting the same problem?
>
>
> --
> ------------------------------------------------------------------------
> Get LLBLGen Pro, productive O/R mapping for .NET:
> http://www.llblgen.com
> My .NET blog: http://weblogs.asp.net/fbouma
> Microsoft MVP (C#)
> ------------------------------------------------------------------------
Is OK if you can't pinpoint the problem, but is it reproducible at your
will? Also, is this a project created with VS 2005 from scratch? Or did you
upgrade it from 2003?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:eZ**************@tk2msftngp13.phx.gbl... I could never pin point the problem. Were you ever able to resolve this
issue?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Do you have a project with the problem that you would be willing to share
with the Microsoft engineer?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:ev**************@TK2MSFTNGP12.phx.gbl...I am getting the same errors. Rearranging the projects might fix it but
that does not explain why the compile will work some times and not
others. If the order of the projects is invalid it shoud fail everytime,
correct?
I also tried the unlocker with no success. Does anyone have an answer
on how to get around this?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
I am currently working with a Microsoft engineer trying to solve this
problem. It's been around 2 weeks and they are still trying to find what
is the cause of this problem is. They are currently escalating the issue
because the problem does not seem to have a straight answer.
Do you have a project that has the problem that you would be willing to
give to the Microsoft engineer? If you do, let me know so I can put you
in touch with the engineer and he can try to reproduce the problem in
his PC and try to narrow down the problem.
Thanks.
"The ants are driving me crazy" <cw******@hotmail.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
> Has anyone found a solution to this problem?
>
>
> Frans Bouma [C# MVP] wrote:
>> Rene wrote:
>>
>> > I am sure that I am closing the application completely. It is the
>> > Visual Studio IDE itself what is not releasing the file. This is
>> > evident because things go back to normal when I close VS 2005 and
>> > reopen it again.
>> >
>> > I have been working on this project for around 2 years using VS
>> > 2003
>> > and never had this problem happened until I started using VS 2005.
>> >
>> > I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled
>> > as
>> > an indication that nothing is running but I continue to get this
>> > error. Perhaps there is some other process in the VS 2005 IDE that
>> > keeps holding on to the file after I stop debugging but I have no
>> > idea what is that process.
>> >
>> > The file name is not "xyz" but is also not a system or VS specific
>> > file, is one of my own. I have even deleted this file hoping that
>> > VS
>> > would recreate the file and snap out of the problem but eventually
>> > it
>> > display the error message again.
>>
>> Also, a virusscanner can lock the file or windows' Indexing service.
>> Be sure both aren't looking in your bin folders. This happens because
>> as soon as the file is written, these services get a signal and get
>> into gear, grab the file and vs.net can't reference it right after
>> that
>> when it compiles a project referencing that dll just written.
>>
>> FB
>>
>> >
>> >
>> >
>> > "Chris Springer" <cs*****@adelphia.net> wrote in message
>> > news:IP********************@adelphia.com...
>> > > You're getting this error because of just what it says...the dll
>> > > is
>> > > in use by another application. Make sure that you are closing
>> > > the
>> > > application that you've compiled and run last to make sure that
>> > > the
>> > > file isn't still being accessed. Could you also please include
>> > > the
>> > > real name of the dll file that you're access...I'm guessing it's
>> > > not really xyz.dll...that might help us figure out what processes
>> > > might be using the dll...
>> > >
>> > > Chris
>> > >
>> > > --
>> > > Securing your systems is much like fighting off disease -- as
>> > > long
>> > > as you maintain basic hygiene, you're likely to be okay, but
>> > > you'll
>> > > never be invulnerable.
>> > >
>> > > Steve Shah - Unix Systems Network Administrator
>> > > "Rene" <no****@nospam.com> wrote in message
>> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
>> > > > I keep getting the following error every time I compile the
>> > > > solution under VS 2005:
>> > > >
>> > >> ----------------
>> > >> Error 5
>> > > >
>> > >> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
>> > The >> process cannot access the file 'bin\Debug\xyz.dll' because
>> > it
>> > is being >> used by another process.
>> > >> ----------------
>> > > >
>> > > >
>> > >> In order to get rid of this problem, I have to constantly close
>> > and >> restart VS 2005. Is anybody else getting the same problem?
>>
>>
>> --
>> ------------------------------------------------------------------------
>> Get LLBLGen Pro, productive O/R mapping for .NET:
>> http://www.llblgen.com
>> My .NET blog: http://weblogs.asp.net/fbouma
>> Microsoft MVP (C#)
>> ------------------------------------------------------------------------
>
We created the project from 2003, and then upgraded to 2005. I have tried to
use the unlocker utility that people have mentioned on other threads but not
to any success.
"Rene" <no****@nospam.com> wrote in message
news:es**************@TK2MSFTNGP10.phx.gbl... Is OK if you can't pinpoint the problem, but is it reproducible at your
will? Also, is this a project created with VS 2005 from scratch? Or did
you upgrade it from 2003?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:eZ**************@tk2msftngp13.phx.gbl...I could never pin point the problem. Were you ever able to resolve this
issue?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... Do you have a project with the problem that you would be willing to
share with the Microsoft engineer?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:ev**************@TK2MSFTNGP12.phx.gbl...
I am getting the same errors. Rearranging the projects might fix it but
that does not explain why the compile will work some times and not
others. If the order of the projects is invalid it shoud fail everytime,
correct?
I also tried the unlocker with no success. Does anyone have an answer
on how to get around this?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
>I am currently working with a Microsoft engineer trying to solve this
>problem. It's been around 2 weeks and they are still trying to find
>what is the cause of this problem is. They are currently escalating the
>issue because the problem does not seem to have a straight answer.
>
> Do you have a project that has the problem that you would be willing
> to give to the Microsoft engineer? If you do, let me know so I can put
> you in touch with the engineer and he can try to reproduce the problem
> in his PC and try to narrow down the problem.
>
> Thanks.
>
>
> "The ants are driving me crazy" <cw******@hotmail.com> wrote in
> message news:11**********************@f14g2000cwb.googlegr oups.com...
>> Has anyone found a solution to this problem?
>>
>>
>> Frans Bouma [C# MVP] wrote:
>>> Rene wrote:
>>>
>>> > I am sure that I am closing the application completely. It is the
>>> > Visual Studio IDE itself what is not releasing the file. This is
>>> > evident because things go back to normal when I close VS 2005 and
>>> > reopen it again.
>>> >
>>> > I have been working on this project for around 2 years using VS
>>> > 2003
>>> > and never had this problem happened until I started using VS 2005.
>>> >
>>> > I can see my "Stop Debugging" Toolbar button (Shift + F5) disabled
>>> > as
>>> > an indication that nothing is running but I continue to get this
>>> > error. Perhaps there is some other process in the VS 2005 IDE that
>>> > keeps holding on to the file after I stop debugging but I have no
>>> > idea what is that process.
>>> >
>>> > The file name is not "xyz" but is also not a system or VS specific
>>> > file, is one of my own. I have even deleted this file hoping that
>>> > VS
>>> > would recreate the file and snap out of the problem but eventually
>>> > it
>>> > display the error message again.
>>>
>>> Also, a virusscanner can lock the file or windows' Indexing service.
>>> Be sure both aren't looking in your bin folders. This happens
>>> because
>>> as soon as the file is written, these services get a signal and get
>>> into gear, grab the file and vs.net can't reference it right after
>>> that
>>> when it compiles a project referencing that dll just written.
>>>
>>> FB
>>>
>>> >
>>> >
>>> >
>>> > "Chris Springer" <cs*****@adelphia.net> wrote in message
>>> > news:IP********************@adelphia.com...
>>> > > You're getting this error because of just what it says...the dll
>>> > > is
>>> > > in use by another application. Make sure that you are closing
>>> > > the
>>> > > application that you've compiled and run last to make sure that
>>> > > the
>>> > > file isn't still being accessed. Could you also please include
>>> > > the
>>> > > real name of the dll file that you're access...I'm guessing it's
>>> > > not really xyz.dll...that might help us figure out what
>>> > > processes
>>> > > might be using the dll...
>>> > >
>>> > > Chris
>>> > >
>>> > > --
>>> > > Securing your systems is much like fighting off disease -- as
>>> > > long
>>> > > as you maintain basic hygiene, you're likely to be okay, but
>>> > > you'll
>>> > > never be invulnerable.
>>> > >
>>> > > Steve Shah - Unix Systems Network Administrator
>>> > > "Rene" <no****@nospam.com> wrote in message
>>> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
>>> > > > I keep getting the following error every time I compile the
>>> > > > solution under VS 2005:
>>> > > >
>>> > >> ----------------
>>> > >> Error 5
>>> > > >
>>> > >> Unable to copy file "obj\Debug\xyz.dll" to "bin\Debug\xyz.dll".
>>> > The >> process cannot access the file 'bin\Debug\xyz.dll' because
>>> > it
>>> > is being >> used by another process.
>>> > >> ----------------
>>> > > >
>>> > > >
>>> > >> In order to get rid of this problem, I have to constantly close
>>> > and >> restart VS 2005. Is anybody else getting the same problem?
>>>
>>>
>>> --
>>> ------------------------------------------------------------------------
>>> Get LLBLGen Pro, productive O/R mapping for .NET:
>>> http://www.llblgen.com
>>> My .NET blog: http://weblogs.asp.net/fbouma
>>> Microsoft MVP (C#)
>>> ------------------------------------------------------------------------
>>
>
>
Well, the Microsoft engineer just gave me some instructions on how to setup
my computer so that it can be monitored to find what is causing the problem.
Not sure how long this is going to take but I will keep posting.
You never told me if you could provide Microsoft your project so they can
troubleshoot what's going on, this may help the speedup the process.
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:es**************@TK2MSFTNGP09.phx.gbl... We created the project from 2003, and then upgraded to 2005. I have tried
to use the unlocker utility that people have mentioned on other threads
but not to any success.
"Rene" <no****@nospam.com> wrote in message
news:es**************@TK2MSFTNGP10.phx.gbl... Is OK if you can't pinpoint the problem, but is it reproducible at your
will? Also, is this a project created with VS 2005 from scratch? Or did
you upgrade it from 2003?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:eZ**************@tk2msftngp13.phx.gbl...I could never pin point the problem. Were you ever able to resolve this
issue?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
Do you have a project with the problem that you would be willing to
share with the Microsoft engineer?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:ev**************@TK2MSFTNGP12.phx.gbl...
>I am getting the same errors. Rearranging the projects might fix it
>but that does not explain why the compile will work some times and not
>others. If the order of the projects is invalid it shoud fail
>everytime, correct?
>
> I also tried the unlocker with no success. Does anyone have an answer
> on how to get around this?
>
>
> "Rene" <no****@nospam.com> wrote in message
> news:%2****************@TK2MSFTNGP09.phx.gbl...
>>I am currently working with a Microsoft engineer trying to solve this
>>problem. It's been around 2 weeks and they are still trying to find
>>what is the cause of this problem is. They are currently escalating
>>the issue because the problem does not seem to have a straight answer.
>>
>> Do you have a project that has the problem that you would be willing
>> to give to the Microsoft engineer? If you do, let me know so I can
>> put you in touch with the engineer and he can try to reproduce the
>> problem in his PC and try to narrow down the problem.
>>
>> Thanks.
>>
>>
>> "The ants are driving me crazy" <cw******@hotmail.com> wrote in
>> message news:11**********************@f14g2000cwb.googlegr oups.com...
>>> Has anyone found a solution to this problem?
>>>
>>>
>>> Frans Bouma [C# MVP] wrote:
>>>> Rene wrote:
>>>>
>>>> > I am sure that I am closing the application completely. It is the
>>>> > Visual Studio IDE itself what is not releasing the file. This is
>>>> > evident because things go back to normal when I close VS 2005 and
>>>> > reopen it again.
>>>> >
>>>> > I have been working on this project for around 2 years using VS
>>>> > 2003
>>>> > and never had this problem happened until I started using VS
>>>> > 2005.
>>>> >
>>>> > I can see my "Stop Debugging" Toolbar button (Shift + F5)
>>>> > disabled as
>>>> > an indication that nothing is running but I continue to get this
>>>> > error. Perhaps there is some other process in the VS 2005 IDE
>>>> > that
>>>> > keeps holding on to the file after I stop debugging but I have no
>>>> > idea what is that process.
>>>> >
>>>> > The file name is not "xyz" but is also not a system or VS
>>>> > specific
>>>> > file, is one of my own. I have even deleted this file hoping that
>>>> > VS
>>>> > would recreate the file and snap out of the problem but
>>>> > eventually it
>>>> > display the error message again.
>>>>
>>>> Also, a virusscanner can lock the file or windows' Indexing
>>>> service.
>>>> Be sure both aren't looking in your bin folders. This happens
>>>> because
>>>> as soon as the file is written, these services get a signal and get
>>>> into gear, grab the file and vs.net can't reference it right after
>>>> that
>>>> when it compiles a project referencing that dll just written.
>>>>
>>>> FB
>>>>
>>>> >
>>>> >
>>>> >
>>>> > "Chris Springer" <cs*****@adelphia.net> wrote in message
>>>> > news:IP********************@adelphia.com...
>>>> > > You're getting this error because of just what it says...the
>>>> > > dll is
>>>> > > in use by another application. Make sure that you are closing
>>>> > > the
>>>> > > application that you've compiled and run last to make sure that
>>>> > > the
>>>> > > file isn't still being accessed. Could you also please include
>>>> > > the
>>>> > > real name of the dll file that you're access...I'm guessing
>>>> > > it's
>>>> > > not really xyz.dll...that might help us figure out what
>>>> > > processes
>>>> > > might be using the dll...
>>>> > >
>>>> > > Chris
>>>> > >
>>>> > > --
>>>> > > Securing your systems is much like fighting off disease -- as
>>>> > > long
>>>> > > as you maintain basic hygiene, you're likely to be okay, but
>>>> > > you'll
>>>> > > never be invulnerable.
>>>> > >
>>>> > > Steve Shah - Unix Systems Network Administrator
>>>> > > "Rene" <no****@nospam.com> wrote in message
>>>> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
>>>> > > > I keep getting the following error every time I compile the
>>>> > > > solution under VS 2005:
>>>> > > >
>>>> > >> ----------------
>>>> > >> Error 5
>>>> > > >
>>>> > >> Unable to copy file "obj\Debug\xyz.dll" to
>>>> > >> "bin\Debug\xyz.dll".
>>>> > The >> process cannot access the file 'bin\Debug\xyz.dll' because
>>>> > it
>>>> > is being >> used by another process.
>>>> > >> ----------------
>>>> > > >
>>>> > > >
>>>> > >> In order to get rid of this problem, I have to constantly
>>>> > >> close
>>>> > and >> restart VS 2005. Is anybody else getting the same problem?
>>>>
>>>>
>>>> --
>>>> ------------------------------------------------------------------------
>>>> Get LLBLGen Pro, productive O/R mapping for .NET:
>>>> http://www.llblgen.com
>>>> My .NET blog: http://weblogs.asp.net/fbouma
>>>> Microsoft MVP (C#)
>>>> ------------------------------------------------------------------------
>>>
>>
>>
>
>
VS only locks one version of the file, and you CAN rename/move it.
You can use the following commands in the pre-build event of the
problem-project to workaround the problem:
if exist "$(TargetPath).locked" del "$(TargetPath).locked"
if not exist "$(TargetPath).locked" move "$(TargetPath)"
"$(TargetPath).locked"
Rene schreef: Well, the Microsoft engineer just gave me some instructions on how to setup
my computer so that it can be monitored to find what is causing the problem.
Not sure how long this is going to take but I will keep posting.
You never told me if you could provide Microsoft your project so they can
troubleshoot what's going on, this may help the speedup the process.
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:es**************@TK2MSFTNGP09.phx.gbl... We created the project from 2003, and then upgraded to 2005. I have tried
to use the unlocker utility that people have mentioned on other threads
but not to any success.
"Rene" <no****@nospam.com> wrote in message
news:es**************@TK2MSFTNGP10.phx.gbl... Is OK if you can't pinpoint the problem, but is it reproducible at your
will? Also, is this a project created with VS 2005 from scratch? Or did
you upgrade it from 2003?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:eZ**************@tk2msftngp13.phx.gbl...
I could never pin point the problem. Were you ever able to resolve this
issue?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
> Do you have a project with the problem that you would be willing to
> share with the Microsoft engineer?
>
>
>
> "MAF" <mf*****@henwoodenergy.com> wrote in message
> news:ev**************@TK2MSFTNGP12.phx.gbl...
>>I am getting the same errors. Rearranging the projects might fix it
>>but that does not explain why the compile will work some times and not
>>others. If the order of the projects is invalid it shoud fail
>>everytime, correct?
>>
>> I also tried the unlocker with no success. Does anyone have an answer
>> on how to get around this?
>>
>>
>> "Rene" <no****@nospam.com> wrote in message
>> news:%2****************@TK2MSFTNGP09.phx.gbl...
>>>I am currently working with a Microsoft engineer trying to solve this
>>>problem. It's been around 2 weeks and they are still trying to find
>>>what is the cause of this problem is. They are currently escalating
>>>the issue because the problem does not seem to have a straight answer.
>>>
>>> Do you have a project that has the problem that you would be willing
>>> to give to the Microsoft engineer? If you do, let me know so I can
>>> put you in touch with the engineer and he can try to reproduce the
>>> problem in his PC and try to narrow down the problem.
>>>
>>> Thanks.
>>>
>>>
>>> "The ants are driving me crazy" <cw******@hotmail.com> wrote in
>>> message news:11**********************@f14g2000cwb.googlegr oups.com...
>>>> Has anyone found a solution to this problem?
>>>>
>>>>
>>>> Frans Bouma [C# MVP] wrote:
>>>>> Rene wrote:
>>>>>
>>>>> > I am sure that I am closing the application completely. It is the
>>>>> > Visual Studio IDE itself what is not releasing the file. This is
>>>>> > evident because things go back to normal when I close VS 2005 and
>>>>> > reopen it again.
>>>>> >
>>>>> > I have been working on this project for around 2 years using VS
>>>>> > 2003
>>>>> > and never had this problem happened until I started using VS
>>>>> > 2005.
>>>>> >
>>>>> > I can see my "Stop Debugging" Toolbar button (Shift + F5)
>>>>> > disabled as
>>>>> > an indication that nothing is running but I continue to get this
>>>>> > error. Perhaps there is some other process in the VS 2005 IDE
>>>>> > that
>>>>> > keeps holding on to the file after I stop debugging but I have no
>>>>> > idea what is that process.
>>>>> >
>>>>> > The file name is not "xyz" but is also not a system or VS
>>>>> > specific
>>>>> > file, is one of my own. I have even deleted this file hoping that
>>>>> > VS
>>>>> > would recreate the file and snap out of the problem but
>>>>> > eventually it
>>>>> > display the error message again.
>>>>>
>>>>> Also, a virusscanner can lock the file or windows' Indexing
>>>>> service.
>>>>> Be sure both aren't looking in your bin folders. This happens
>>>>> because
>>>>> as soon as the file is written, these services get a signal and get
>>>>> into gear, grab the file and vs.net can't reference it right after
>>>>> that
>>>>> when it compiles a project referencing that dll just written.
>>>>>
>>>>> FB
>>>>>
>>>>> >
>>>>> >
>>>>> >
>>>>> > "Chris Springer" <cs*****@adelphia.net> wrote in message
>>>>> > news:IP********************@adelphia.com...
>>>>> > > You're getting this error because of just what it says...the
>>>>> > > dll is
>>>>> > > in use by another application. Make sure that you are closing
>>>>> > > the
>>>>> > > application that you've compiled and run last to make sure that
>>>>> > > the
>>>>> > > file isn't still being accessed. Could you also please include
>>>>> > > the
>>>>> > > real name of the dll file that you're access...I'm guessing
>>>>> > > it's
>>>>> > > not really xyz.dll...that might help us figure out what
>>>>> > > processes
>>>>> > > might be using the dll...
>>>>> > >
>>>>> > > Chris
>>>>> > >
>>>>> > > --
>>>>> > > Securing your systems is much like fighting off disease -- as
>>>>> > > long
>>>>> > > as you maintain basic hygiene, you're likely to be okay, but
>>>>> > > you'll
>>>>> > > never be invulnerable.
>>>>> > >
>>>>> > > Steve Shah - Unix Systems Network Administrator
>>>>> > > "Rene" <no****@nospam.com> wrote in message
>>>>> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
>>>>> > > > I keep getting the following error every time I compile the
>>>>> > > > solution under VS 2005:
>>>>> > > >
>>>>> > >> ----------------
>>>>> > >> Error 5
>>>>> > > >
>>>>> > >> Unable to copy file "obj\Debug\xyz.dll" to
>>>>> > >> "bin\Debug\xyz.dll".
>>>>> > The >> process cannot access the file 'bin\Debug\xyz.dll' because
>>>>> > it
>>>>> > is being >> used by another process.
>>>>> > >> ----------------
>>>>> > > >
>>>>> > > >
>>>>> > >> In order to get rid of this problem, I have to constantly
>>>>> > >> close
>>>>> > and >> restart VS 2005. Is anybody else getting the same problem?
>>>>>
>>>>>
>>>>> --
>>>>> ------------------------------------------------------------------------
>>>>> Get LLBLGen Pro, productive O/R mapping for .NET:
>>>>> http://www.llblgen.com
>>>>> My .NET blog: http://weblogs.asp.net/fbouma
>>>>> Microsoft MVP (C#)
>>>>> ------------------------------------------------------------------------
>>>>
>>>
>>>
>>
>>
>
>
> if exist "$(TargetPath).locked" del "$(TargetPath).locked" if exist "$(TargetPath)" if not exist "$(TargetPath).locked" move "$(TargetPath)" "$(TargetPath).locked"
Sorry I have not being able to create a sample project that will cause the
problem.
"Rene" <no****@nospam.com> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl... Well, the Microsoft engineer just gave me some instructions on how to
setup my computer so that it can be monitored to find what is causing the
problem. Not sure how long this is going to take but I will keep posting.
You never told me if you could provide Microsoft your project so they can
troubleshoot what's going on, this may help the speedup the process.
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:es**************@TK2MSFTNGP09.phx.gbl... We created the project from 2003, and then upgraded to 2005. I have tried
to use the unlocker utility that people have mentioned on other threads
but not to any success.
"Rene" <no****@nospam.com> wrote in message
news:es**************@TK2MSFTNGP10.phx.gbl... Is OK if you can't pinpoint the problem, but is it reproducible at your
will? Also, is this a project created with VS 2005 from scratch? Or did
you upgrade it from 2003?
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:eZ**************@tk2msftngp13.phx.gbl...
I could never pin point the problem. Were you ever able to resolve this
issue?
"Rene" <no****@nospam.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...
> Do you have a project with the problem that you would be willing to
> share with the Microsoft engineer?
>
>
>
> "MAF" <mf*****@henwoodenergy.com> wrote in message
> news:ev**************@TK2MSFTNGP12.phx.gbl...
>>I am getting the same errors. Rearranging the projects might fix it
>>but that does not explain why the compile will work some times and not
>>others. If the order of the projects is invalid it shoud fail
>>everytime, correct?
>>
>> I also tried the unlocker with no success. Does anyone have an
>> answer on how to get around this?
>>
>>
>> "Rene" <no****@nospam.com> wrote in message
>> news:%2****************@TK2MSFTNGP09.phx.gbl...
>>>I am currently working with a Microsoft engineer trying to solve this
>>>problem. It's been around 2 weeks and they are still trying to find
>>>what is the cause of this problem is. They are currently escalating
>>>the issue because the problem does not seem to have a straight
>>>answer.
>>>
>>> Do you have a project that has the problem that you would be willing
>>> to give to the Microsoft engineer? If you do, let me know so I can
>>> put you in touch with the engineer and he can try to reproduce the
>>> problem in his PC and try to narrow down the problem.
>>>
>>> Thanks.
>>>
>>>
>>> "The ants are driving me crazy" <cw******@hotmail.com> wrote in
>>> message
>>> news:11**********************@f14g2000cwb.googlegr oups.com...
>>>> Has anyone found a solution to this problem?
>>>>
>>>>
>>>> Frans Bouma [C# MVP] wrote:
>>>>> Rene wrote:
>>>>>
>>>>> > I am sure that I am closing the application completely. It is
>>>>> > the
>>>>> > Visual Studio IDE itself what is not releasing the file. This is
>>>>> > evident because things go back to normal when I close VS 2005
>>>>> > and
>>>>> > reopen it again.
>>>>> >
>>>>> > I have been working on this project for around 2 years using VS
>>>>> > 2003
>>>>> > and never had this problem happened until I started using VS
>>>>> > 2005.
>>>>> >
>>>>> > I can see my "Stop Debugging" Toolbar button (Shift + F5)
>>>>> > disabled as
>>>>> > an indication that nothing is running but I continue to get this
>>>>> > error. Perhaps there is some other process in the VS 2005 IDE
>>>>> > that
>>>>> > keeps holding on to the file after I stop debugging but I have
>>>>> > no
>>>>> > idea what is that process.
>>>>> >
>>>>> > The file name is not "xyz" but is also not a system or VS
>>>>> > specific
>>>>> > file, is one of my own. I have even deleted this file hoping
>>>>> > that VS
>>>>> > would recreate the file and snap out of the problem but
>>>>> > eventually it
>>>>> > display the error message again.
>>>>>
>>>>> Also, a virusscanner can lock the file or windows' Indexing
>>>>> service.
>>>>> Be sure both aren't looking in your bin folders. This happens
>>>>> because
>>>>> as soon as the file is written, these services get a signal and
>>>>> get
>>>>> into gear, grab the file and vs.net can't reference it right after
>>>>> that
>>>>> when it compiles a project referencing that dll just written.
>>>>>
>>>>> FB
>>>>>
>>>>> >
>>>>> >
>>>>> >
>>>>> > "Chris Springer" <cs*****@adelphia.net> wrote in message
>>>>> > news:IP********************@adelphia.com...
>>>>> > > You're getting this error because of just what it says...the
>>>>> > > dll is
>>>>> > > in use by another application. Make sure that you are closing
>>>>> > > the
>>>>> > > application that you've compiled and run last to make sure
>>>>> > > that the
>>>>> > > file isn't still being accessed. Could you also please
>>>>> > > include the
>>>>> > > real name of the dll file that you're access...I'm guessing
>>>>> > > it's
>>>>> > > not really xyz.dll...that might help us figure out what
>>>>> > > processes
>>>>> > > might be using the dll...
>>>>> > >
>>>>> > > Chris
>>>>> > >
>>>>> > > --
>>>>> > > Securing your systems is much like fighting off disease -- as
>>>>> > > long
>>>>> > > as you maintain basic hygiene, you're likely to be okay, but
>>>>> > > you'll
>>>>> > > never be invulnerable.
>>>>> > >
>>>>> > > Steve Shah - Unix Systems Network Administrator
>>>>> > > "Rene" <no****@nospam.com> wrote in message
>>>>> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
>>>>> > > > I keep getting the following error every time I compile the
>>>>> > > > solution under VS 2005:
>>>>> > > >
>>>>> > >> ----------------
>>>>> > >> Error 5
>>>>> > > >
>>>>> > >> Unable to copy file "obj\Debug\xyz.dll" to
>>>>> > >> "bin\Debug\xyz.dll".
>>>>> > The >> process cannot access the file 'bin\Debug\xyz.dll'
>>>>> > because it
>>>>> > is being >> used by another process.
>>>>> > >> ----------------
>>>>> > > >
>>>>> > > >
>>>>> > >> In order to get rid of this problem, I have to constantly
>>>>> > >> close
>>>>> > and >> restart VS 2005. Is anybody else getting the same
>>>>> > problem?
>>>>>
>>>>>
>>>>> --
>>>>> ------------------------------------------------------------------------
>>>>> Get LLBLGen Pro, productive O/R mapping for .NET:
>>>>> http://www.llblgen.com
>>>>> My .NET blog: http://weblogs.asp.net/fbouma
>>>>> Microsoft MVP (C#)
>>>>> ------------------------------------------------------------------------
>>>>
>>>
>>>
>>
>>
>
>
Assuming that the file being locked is the following file:
C:\FileWithProblems.dll
Could you please post what *exactly* do I have to type on the pre-build
event text box? I am wondering if I am not typing the right string.
Thanks.
<c0*@hotmail.com> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com... VS only locks one version of the file, and you CAN rename/move it.
You can use the following commands in the pre-build event of the
problem-project to workaround the problem:
if exist "$(TargetPath).locked" del "$(TargetPath).locked"
if not exist "$(TargetPath).locked" move "$(TargetPath)"
"$(TargetPath).locked"
Rene schreef:
Well, the Microsoft engineer just gave me some instructions on how to
setup
my computer so that it can be monitored to find what is causing the
problem.
Not sure how long this is going to take but I will keep posting.
You never told me if you could provide Microsoft your project so they can
troubleshoot what's going on, this may help the speedup the process.
"MAF" <mf*****@henwoodenergy.com> wrote in message
news:es**************@TK2MSFTNGP09.phx.gbl... > We created the project from 2003, and then upgraded to 2005. I have
> tried
> to use the unlocker utility that people have mentioned on other threads
> but not to any success.
>
> "Rene" <no****@nospam.com> wrote in message
> news:es**************@TK2MSFTNGP10.phx.gbl...
>> Is OK if you can't pinpoint the problem, but is it reproducible at
>> your
>> will? Also, is this a project created with VS 2005 from scratch? Or
>> did
>> you upgrade it from 2003?
>>
>>
>> "MAF" <mf*****@henwoodenergy.com> wrote in message
>> news:eZ**************@tk2msftngp13.phx.gbl...
>>>I could never pin point the problem. Were you ever able to resolve
>>>this
>>>issue?
>>>
>>>
>>> "Rene" <no****@nospam.com> wrote in message
>>> news:%2****************@TK2MSFTNGP10.phx.gbl...
>>>> Do you have a project with the problem that you would be willing to
>>>> share with the Microsoft engineer?
>>>>
>>>>
>>>>
>>>> "MAF" <mf*****@henwoodenergy.com> wrote in message
>>>> news:ev**************@TK2MSFTNGP12.phx.gbl...
>>>>>I am getting the same errors. Rearranging the projects might fix it
>>>>>but that does not explain why the compile will work some times and
>>>>>not
>>>>>others. If the order of the projects is invalid it shoud fail
>>>>>everytime, correct?
>>>>>
>>>>> I also tried the unlocker with no success. Does anyone have an
>>>>> answer
>>>>> on how to get around this?
>>>>>
>>>>>
>>>>> "Rene" <no****@nospam.com> wrote in message
>>>>> news:%2****************@TK2MSFTNGP09.phx.gbl...
>>>>>>I am currently working with a Microsoft engineer trying to solve
>>>>>>this
>>>>>>problem. It's been around 2 weeks and they are still trying to find
>>>>>>what is the cause of this problem is. They are currently escalating
>>>>>>the issue because the problem does not seem to have a straight
>>>>>>answer.
>>>>>>
>>>>>> Do you have a project that has the problem that you would be
>>>>>> willing
>>>>>> to give to the Microsoft engineer? If you do, let me know so I can
>>>>>> put you in touch with the engineer and he can try to reproduce the
>>>>>> problem in his PC and try to narrow down the problem.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>>
>>>>>> "The ants are driving me crazy" <cw******@hotmail.com> wrote in
>>>>>> message
>>>>>> news:11**********************@f14g2000cwb.googlegr oups.com...
>>>>>>> Has anyone found a solution to this problem?
>>>>>>>
>>>>>>>
>>>>>>> Frans Bouma [C# MVP] wrote:
>>>>>>>> Rene wrote:
>>>>>>>>
>>>>>>>> > I am sure that I am closing the application completely. It is
>>>>>>>> > the
>>>>>>>> > Visual Studio IDE itself what is not releasing the file. This
>>>>>>>> > is
>>>>>>>> > evident because things go back to normal when I close VS 2005
>>>>>>>> > and
>>>>>>>> > reopen it again.
>>>>>>>> >
>>>>>>>> > I have been working on this project for around 2 years using
>>>>>>>> > VS
>>>>>>>> > 2003
>>>>>>>> > and never had this problem happened until I started using VS
>>>>>>>> > 2005.
>>>>>>>> >
>>>>>>>> > I can see my "Stop Debugging" Toolbar button (Shift + F5)
>>>>>>>> > disabled as
>>>>>>>> > an indication that nothing is running but I continue to get
>>>>>>>> > this
>>>>>>>> > error. Perhaps there is some other process in the VS 2005 IDE
>>>>>>>> > that
>>>>>>>> > keeps holding on to the file after I stop debugging but I have
>>>>>>>> > no
>>>>>>>> > idea what is that process.
>>>>>>>> >
>>>>>>>> > The file name is not "xyz" but is also not a system or VS
>>>>>>>> > specific
>>>>>>>> > file, is one of my own. I have even deleted this file hoping
>>>>>>>> > that
>>>>>>>> > VS
>>>>>>>> > would recreate the file and snap out of the problem but
>>>>>>>> > eventually it
>>>>>>>> > display the error message again.
>>>>>>>>
>>>>>>>> Also, a virusscanner can lock the file or windows' Indexing
>>>>>>>> service.
>>>>>>>> Be sure both aren't looking in your bin folders. This happens
>>>>>>>> because
>>>>>>>> as soon as the file is written, these services get a signal and
>>>>>>>> get
>>>>>>>> into gear, grab the file and vs.net can't reference it right
>>>>>>>> after
>>>>>>>> that
>>>>>>>> when it compiles a project referencing that dll just written.
>>>>>>>>
>>>>>>>> FB
>>>>>>>>
>>>>>>>> >
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > "Chris Springer" <cs*****@adelphia.net> wrote in message
>>>>>>>> > news:IP********************@adelphia.com...
>>>>>>>> > > You're getting this error because of just what it says...the
>>>>>>>> > > dll is
>>>>>>>> > > in use by another application. Make sure that you are
>>>>>>>> > > closing
>>>>>>>> > > the
>>>>>>>> > > application that you've compiled and run last to make sure
>>>>>>>> > > that
>>>>>>>> > > the
>>>>>>>> > > file isn't still being accessed. Could you also please
>>>>>>>> > > include
>>>>>>>> > > the
>>>>>>>> > > real name of the dll file that you're access...I'm guessing
>>>>>>>> > > it's
>>>>>>>> > > not really xyz.dll...that might help us figure out what
>>>>>>>> > > processes
>>>>>>>> > > might be using the dll...
>>>>>>>> > >
>>>>>>>> > > Chris
>>>>>>>> > >
>>>>>>>> > > --
>>>>>>>> > > Securing your systems is much like fighting off disease --
>>>>>>>> > > as
>>>>>>>> > > long
>>>>>>>> > > as you maintain basic hygiene, you're likely to be okay, but
>>>>>>>> > > you'll
>>>>>>>> > > never be invulnerable.
>>>>>>>> > >
>>>>>>>> > > Steve Shah - Unix Systems Network Administrator
>>>>>>>> > > "Rene" <no****@nospam.com> wrote in message
>>>>>>>> > > news:OH**************@TK2MSFTNGP14.phx.gbl...
>>>>>>>> > > > I keep getting the following error every time I compile
>>>>>>>> > > > the
>>>>>>>> > > > solution under VS 2005:
>>>>>>>> > > >
>>>>>>>> > >> ----------------
>>>>>>>> > >> Error 5
>>>>>>>> > > >
>>>>>>>> > >> Unable to copy file "obj\Debug\xyz.dll" to
>>>>>>>> > >> "bin\Debug\xyz.dll".
>>>>>>>> > The >> process cannot access the file 'bin\Debug\xyz.dll'
>>>>>>>> > because
>>>>>>>> > it
>>>>>>>> > is being >> used by another process.
>>>>>>>> > >> ----------------
>>>>>>>> > > >
>>>>>>>> > > >
>>>>>>>> > >> In order to get rid of this problem, I have to constantly
>>>>>>>> > >> close
>>>>>>>> > and >> restart VS 2005. Is anybody else getting the same
>>>>>>>> > problem?
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>> Get LLBLGen Pro, productive O/R mapping for .NET:
>>>>>>>> http://www.llblgen.com
>>>>>>>> My .NET blog: http://weblogs.asp.net/fbouma
>>>>>>>> Microsoft MVP (C#)
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Type two lines,
Line one:
if exist "$(TargetPath).locked" del "$(TargetPath).locked"
Line two:
if exist "$(TargetPath)" if not exist "$(TargetPath).locked" move
"$(TargetPath)" "$(TargetPath).locked"
Hey, that worked! I've looked in a ton of forums and am really psyched
to have found that. I was experiencing it in a vs2003 upgraded to
vs2005 multi project winform vss connected behemoth and your pre-build
event worked like a charm with this issue. kudos
Another Kudos from me...
The Pre-compile code solved my problem...
THANK YOU all in caps...
PS:
For anyone that cannot reproduce, I have a prety stable way of
re-creating this:
Create a solution
Create 4 class library projects LibA (Data), LibB (DAL) LibC (Business)
and LibD (Facade)
Create 1 Window control Library project ProjA (Common UserControls) and
1 Winforms application ProjB (Executable)
Reference LibA in all the other projects
Reference LibB in LibC
Reference LibC in LibD
Reference LibD in ProjA and ProjB
Reference ProjA in Proj B
This would be a common setup for a Data, DAL, Business, Facade,
CommonUsercontrols and winforms solution, if anyone is using that
approach anymore...
add a dataset in LibA
Add a component in each of the other Libraries, drag-drop this dataset
on them
Add a Usercontrol in ProjA, drop the dataset + and the component from
libD on the usercontrol
Add a winforms to ProjB
Drag-drop the usercontrol in ProjA to this form.
Drop a button, create a handler but do not place any code in it.
Put a breakpoint in the buttonclick event handler
Compile > Compiles successfully
run debug
Click the button
add some dummy code (use edit-and continue)
stop debugging
add more code in LibA component
Compile > Get the error
LibA gives the error ma********@gmail.com wrote: Hey, that worked! I've looked in a ton of forums and am really psyched
to have found that. I was experiencing it in a vs2003 upgraded to
vs2005 multi project winform vss connected behemoth and your pre-build
event worked like a charm with this issue. kudos
So what was the over all solution?
<du*******@gmail.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com... Another Kudos from me...
The Pre-compile code solved my problem...
THANK YOU all in caps...
PS:
For anyone that cannot reproduce, I have a prety stable way of
re-creating this:
Create a solution
Create 4 class library projects LibA (Data), LibB (DAL) LibC (Business)
and LibD (Facade)
Create 1 Window control Library project ProjA (Common UserControls) and
1 Winforms application ProjB (Executable)
Reference LibA in all the other projects
Reference LibB in LibC
Reference LibC in LibD
Reference LibD in ProjA and ProjB
Reference ProjA in Proj B
This would be a common setup for a Data, DAL, Business, Facade,
CommonUsercontrols and winforms solution, if anyone is using that
approach anymore...
add a dataset in LibA
Add a component in each of the other Libraries, drag-drop this dataset
on them
Add a Usercontrol in ProjA, drop the dataset + and the component from
libD on the usercontrol
Add a winforms to ProjB
Drag-drop the usercontrol in ProjA to this form.
Drop a button, create a handler but do not place any code in it.
Put a breakpoint in the buttonclick event handler
Compile > Compiles successfully
run debug
Click the button
add some dummy code (use edit-and continue)
stop debugging
add more code in LibA component
Compile > Get the error
LibA gives the error
ma********@gmail.com wrote: Hey, that worked! I've looked in a ton of forums and am really psyched
to have found that. I was experiencing it in a vs2003 upgraded to
vs2005 multi project winform vss connected behemoth and your pre-build
event worked like a charm with this issue. kudos This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Mark Broadbent |
last post by:
This post is not intended in inflame, so please provide only positive or
informative replies.
Personally I'm getting a little fed up over certain changes to Framework
classes and such -whereby...
|
by: samsonfr |
last post by:
Hello,
I have read KB 814472 and the article "How To: Remove Dependency on
_vcclrit.h"
(http://msdn2.microsoft.com/en-us/library/ms173267(en-us,vs.80).aspx)
which confirmed that VS.NET 2005...
|
by: Shapper |
last post by:
Hello,
I am starting 2 new projects to deliver in January 2006.
I want to create them in Asp.Net 2.0 using Visual Studio 2005.
All my clients web sites are Visual Studio 2003 projects in...
|
by: Hardy Wang |
last post by:
Hi all,
I just installed VS.Net 2005 and tried to play with it. I have following
questions
1) I created a web project, I compile it, unlike VS.Net 2003 but I could not
find any DLL files in BIN...
|
by: Mike Owen |
last post by:
Hi,
I am trying to pre-compile a project prior using ASP.Net 2.0, VS 2005, to
putting it onto a live server.
The reason for doing this is that other people have access to the server,
and I...
|
by: WT |
last post by:
Hello,
I have been publishing my web site many times to the remote where resides my
final web site.
Everything was ok, but to-day, without any configuration change, vs doesn't
copy final files...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| |
