Link error
-
Hello All, A couple of weeks ago I started getting the following error, but I don't know what is causing it. LINK : fatal error LNK1168: cannot open ..\Bin\Administrator.exe for writing It happens after I've run the application from with Visual Studio (2003), but I'm sure nothing is leaking so that something would keep the file in use. I use Boundschecker to check for leaks. My work around is to go to the Windows Explorer and delete the executable from there. That always works so the file isn't "in use" from an operating system point of view. Any ideas as to what changed or what causes this quite irritating problem??? Thanks in advance. Koolski
-
Hello All, A couple of weeks ago I started getting the following error, but I don't know what is causing it. LINK : fatal error LNK1168: cannot open ..\Bin\Administrator.exe for writing It happens after I've run the application from with Visual Studio (2003), but I'm sure nothing is leaking so that something would keep the file in use. I use Boundschecker to check for leaks. My work around is to go to the Windows Explorer and delete the executable from there. That always works so the file isn't "in use" from an operating system point of view. Any ideas as to what changed or what causes this quite irritating problem??? Thanks in advance. Koolski
Hi, as long as Administrator.exe is still running (hence visible in Task Manager) the file is locked and cannot be replaced by any program, including Visual. The easiest way to keep a program running even when its main Form got closed, is by having one or more threads that haven't finished yet *and* don't have their IsBackground property set true. A background thread does not keep an app from exiting, a foreground one does. :)
Luc Pattyn [Forum Guidelines] [My Articles]
Fixturized forever. :confused:
-
Hi, as long as Administrator.exe is still running (hence visible in Task Manager) the file is locked and cannot be replaced by any program, including Visual. The easiest way to keep a program running even when its main Form got closed, is by having one or more threads that haven't finished yet *and* don't have their IsBackground property set true. A background thread does not keep an app from exiting, a foreground one does. :)
Luc Pattyn [Forum Guidelines] [My Articles]
Fixturized forever. :confused:
Luc Pattyn wrote:
as long as Administrator.exe is still running (hence visible in Task Manager) the file is locked and cannot be replaced by any program, including Visual
The thing is though, it's not visible in the task manager. No applications and no processes. It appears to be completely exited when you look at the output window in Visual Studio. Any other ideas?
-
Luc Pattyn wrote:
as long as Administrator.exe is still running (hence visible in Task Manager) the file is locked and cannot be replaced by any program, including Visual
The thing is though, it's not visible in the task manager. No applications and no processes. It appears to be completely exited when you look at the output window in Visual Studio. Any other ideas?
After being downvoted all my remaining ideas suddenly have vanished. :~
Luc Pattyn [Forum Guidelines] [My Articles]
Fixturized forever. :confused:
-
After being downvoted all my remaining ideas suddenly have vanished. :~
Luc Pattyn [Forum Guidelines] [My Articles]
Fixturized forever. :confused:
Whatever... :confused: The prompt asks whether this was helpful; yes or no, not rate it on a scale of 1 to 10 -- Your response was, in essence, "if it's still running, then it's still running". I don't bother someone else until I have done my work, eliminating the obvious. I guess honesty isn't the best policy.