FIX: Path Problems Using Project on Network Server

• Microsoft Visual Basic, Learning, Professional, and Enterprise Editions for Windows, version 5.0

SYMPTOMS

Saving 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.

CAUSE

This problem is caused when Visual Basic attempts to store the path to the EXE relative to the Project files.

RESOLUTION

Keep 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.

For more information on the Visual Studio 97 Service Pack 2, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q170365
   TITLE     : INFO: Visual Studio 97 Service Packs - What, Where, and Why

   ARTICLE-ID: Q171554
   TITLE     : INFO: Visual Basic 5.0 Fixes in Visual Studio 97
               Service Pack 2

MORE INFORMATION

Steps to Reproduce Behavior

This requires two machines;

1. Create two shares on a system, for example:

         \\MyComputer\Share1
         \\MyComputer\Share2
   

2. From a second machine, create a new standard EXE project.

3. Save the project file and Form1 to \\MyComputer\Share1.

4. Build an EXE and save it to \\MyComputer\Share2.

5. Close the project.

6. Re-open the project.

7. Choose Build Exe from the file menu.

Observed Behavior

In the Build EXE dialog window, note that the path to the EXE is incorrect; the path appears as:

   \\<Path to Project>\..\<Path to Exe>.Exe

   "\\<Path to Project>\..\<Path to Exe>.Exe
   The filename is not valid"

Keywords          : vb5all VS97FixlistSP3 VS97FixlistSP2 VB5FixlistSP2
Version           : 5.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbservicepack