Windows XP 上的 VB6 - LINK：致命错误 LNK1104：无法打开文件 "Path/To/File/Its/Making"
VB6 on Windows XP - LINK : fatal error LNK1104: cannot open file "Path/To/File/Its/Making"
我将继续维护几个名为 "Legacy Projects" 的程序。为此，我有一个单独的 Windows XP 系统。
其中大部分是 VB6 程序。我有一个我被迫做出改变。只是现在它拒绝生成新的可执行文件，并给出上述错误消息：
LINK : fatal error LNK1104: cannot open file "C:\Documents And Settings\Me\My Documents\VB6 Projects\Some Directory Path Name\MyProjectDirectory\MyProjectExecutable.exe
我打开了一个旧版本的项目，它编译并创建了可执行文件。
出于沮丧，我创建了一个全新的项目，将源文件（表单、模块和 class 模块）移到其中，然后再次尝试。它失败了。再次。还是.
为什么。
信息不充分我来猜一猜
PRB: LINK Fatal Error LNK1104 Cannot Open File
Q166470
SYMPTOMS
When compiling an ActiveX component with binary compatibility set to the same file the compile is attempting to overwrite, the following error occurs:
LINK fatal error LNK1104 cannot open file.
RESOLUTION
To work around this problem, copy the ActiveX executable or DLL to a separate directory. Set binary compatibility to the copied file, and
compile to the original directory. This procedure is described in
Microsoft Visual Basic Books Online.
更一般地说，您可以查找所有 MS 语言都使用的 VC++ 链接器参考。
Linker Tools Error LNK1104 cannot open file "filename"
The tool could not open the given file.
Tips
One of the following may be a cause:
There was not enough disk space.
The file does not exist.
The filename or its path was incorrectly specified.
The specified drive is invalid.
The file does not have the appropriate permissions.
The path for filename expands to more than 260 characters.
If the given file is named LNKn, which is a filename generated by the
linker for a temporary file, then the directory specified in the TMP
environment variable may not exist, or more than one directory is
specified for the TMP environment variable. (Only one directory path
should be specified for the TMP environment variable.)
If the error occurs on the executable filename, an earlier version of
the executable may still be running. You will need to terminate the
executable before linking it. In Windows NT or Windows 95 you can use
the utility PVIEW to look for and kill instances of the application.
PVIEW.EXE is shipped with Visual C++.
If the error message occurs for a library name, and you recently
ported the .MAK file from a previous Microsoft Visual C++ development
system, the library may no longer be valid. Ensure that the library
still exists in this circumstance.
我将继续维护几个名为 "Legacy Projects" 的程序。为此，我有一个单独的 Windows XP 系统。
其中大部分是 VB6 程序。我有一个我被迫做出改变。只是现在它拒绝生成新的可执行文件，并给出上述错误消息：
LINK : fatal error LNK1104: cannot open file "C:\Documents And Settings\Me\My Documents\VB6 Projects\Some Directory Path Name\MyProjectDirectory\MyProjectExecutable.exe
我打开了一个旧版本的项目，它编译并创建了可执行文件。
出于沮丧，我创建了一个全新的项目，将源文件（表单、模块和 class 模块）移到其中，然后再次尝试。它失败了。再次。还是.
为什么。
信息不充分我来猜一猜
PRB: LINK Fatal Error LNK1104 Cannot Open File
Q166470
SYMPTOMS
When compiling an ActiveX component with binary compatibility set to the same file the compile is attempting to overwrite, the following error occurs:
LINK fatal error LNK1104 cannot open file.RESOLUTION
To work around this problem, copy the ActiveX executable or DLL to a separate directory. Set binary compatibility to the copied file, and compile to the original directory. This procedure is described in Microsoft Visual Basic Books Online.
更一般地说，您可以查找所有 MS 语言都使用的 VC++ 链接器参考。
Linker Tools Error LNK1104 cannot open file "filename"
The tool could not open the given file.
Tips
One of the following may be a cause:
There was not enough disk space.
The file does not exist.
The filename or its path was incorrectly specified.
The specified drive is invalid.
The file does not have the appropriate permissions.
The path for filename expands to more than 260 characters.
If the given file is named LNKn, which is a filename generated by the linker for a temporary file, then the directory specified in the TMP environment variable may not exist, or more than one directory is specified for the TMP environment variable. (Only one directory path should be specified for the TMP environment variable.)
If the error occurs on the executable filename, an earlier version of the executable may still be running. You will need to terminate the executable before linking it. In Windows NT or Windows 95 you can use the utility PVIEW to look for and kill instances of the application. PVIEW.EXE is shipped with Visual C++.
If the error message occurs for a library name, and you recently ported the .MAK file from a previous Microsoft Visual C++ development system, the library may no longer be valid. Ensure that the library still exists in this circumstance.