Why does VS2008 display this error despite a successful compilation of code..
Error 1 fatal error LNK1105: cannot close file 'd:vs2008win32projectDebugwin32project.exe' win32project win32project
How does one close the EXE file to avoid this error being generated?
Comments
: of code..
:
: Error 1 fatal error LNK1105: cannot close file
: 'd:vs2008win32projectDebugwin32project.exe' win32project win32pro
: ject
:
:
: How does one close the EXE file to avoid this error being generated?
:
Clean out your debug directory, reboot the machine, and try again.
It could be either a version of the program still running in the background, or something funny with an existing file in the directory.
It is unlikely to be a common internal error that means you can never write an executable, or Microsoft would have caught it early on.
: : of code..
: :
: : Error 1 fatal error LNK1105: cannot close file
: : 'd:vs2008win32projectDebugwin32project.exe' win32project win32pro
: : ject
: :
: :
: : How does one close the EXE file to avoid this error being generated?
: :
: Clean out your debug directory, reboot the machine, and try again.
:
: It could be either a version of the program still running in the
: background, or something funny with an existing file in the
: directory.
: It is unlikely to be a common internal error that means you can
: never write an executable, or Microsoft would have caught it early
: on.
:
:
:
:I wish that were a version of the program still running in the background but it doesn't seem to be so. This happens irrespective of whether I have written a console application or a Win32 one. I am confident that this is no internal error but rather something happening at my end. I cannot even run the program using Ctrl + F5 without this error being generated. To still manage to run an EXE I have to first Rebuild the project and then go in for Ctrl+F5. Rather annoying hence this post. Hope somebody can clear this mess for me.
: : : of code..
: : :
: : : Error 1 fatal error LNK1105: cannot close file
: : : 'd:vs2008win32projectDebugwin32project.exe' win32project win32pro
: : : ject
: : :
: : :
: : : How does one close the EXE file to avoid this error being generated?
: : :
: : Clean out your debug directory, reboot the machine, and try again.
: :
: : It could be either a version of the program still running in the
: : background, or something funny with an existing file in the
: : directory.
: : It is unlikely to be a common internal error that means you can
: : never write an executable, or Microsoft would have caught it early
: : on.
: :
: :
: :
: :I wish that were a version of the program still running in the
: background but it doesn't seem to be so. This happens irrespective
: of whether I have written a console application or a Win32 one. I am
: confident that this is no internal error but rather something
: happening at my end. I cannot even run the program using Ctrl + F5
: without this error being generated. To still manage to run an EXE I
: have to first Rebuild the project and then go in for Ctrl+F5.
: Rather annoying hence this post. Hope somebody can clear this mess
: for me.
[color=Blue]Usually Google for an error code. If you do it using "LNK1105" - you get this:
[link=http://msdn.microsoft.com/en-us/library/80z106bx.aspx]http://msdn.microsoft.com/en-us/library/80z106bx.aspx[/link]
Seems unconnected... how does inability to close a file affected by a disk full condition?!! but check it anyway.[/color]