The information in this article applies to:
SYMPTOMSSaving a project to one network share and creating the exe on a different network share causes Visual Basic to generate an invalid path to the EXE file. CAUSEThis problem is caused when Visual Basic attempts to store the path to the EXE relative to the Project files. RESOLUTIONKeep EXE and Project on same share or upgrade to Visual Studio 97 Service Pack 2. STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. This bug has been fixed in Visual Studio
97 Service Pack 2. Q170365 INFO: Visual Studio 97 Service Packs - What, Where, and WhyFor a list of the Visual Basic 5.0 bugs that were fixed in the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base: Q171554 INFO: Visual Basic 5.0 Fixes in Visual Studio 97 Service Pack 2 MORE INFORMATIONSteps to Reproduce BehaviorThis requires two machines;
Observed BehaviorIn the Build EXE dialog window, note that the path to the EXE is incorrect; the path appears as:
Without changing anything, click OK. You will receive an error:
Additional query words:
Keywords : kbVBp500 kbVS97sp2fix kbGrpVB kbvbp500sp2fix |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |