PRB: Version Number Not Incrementing Using Command Line /Make

Last reviewed: September 11, 1997
Article ID: Q173650
The information in this article applies to:
  • Microsoft Visual Basic Control Creation, Learning, Professional, and Enterprise Editions for Windows, version 5.0
  • Microsoft Visual Basic Standard, Professional, and Enterprise Editions for Windows, version 4.0

SYMPTOMS

When making an executable file using the Visual Basic command-line argument /make or /m, the Revision Version Number is incremented only the first time even though Auto Increment was checked in the Project Properties dialog box before the project was saved.

RESOLUTION

To maintain accurate versioning in your applications, compile the executable file via the Visual Basic Integrated Development Environment (IDE).

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The Visual Basic /make or /m command-line argument is designed to adhere to the Path, EXEName, and Title properties of the App object. It is not designed to adhere to the versioning information or the Auto Increment property of the project.

Steps to Reproduce Behavior

  1. Create a new Standard EXE project. Form1 is added by default.

  2. On the File menu, click Make Project1.exe.

  3. In the Make Project dialog box, click the Options button.

  4. In the Project Properties dialog box, change the Major Version Number to 2, the Minor Version Number to 2, the Revision Version Number to 2, and select Auto Increment.

  5. Click OK to return to the Make Project dialog box; then click OK to create the executable.

  6. Save the project and exit Visual Basic.

  7. Using the Microsoft Windows Explorer, locate the Project1.exe file, right-click to select the file, click Properties on the menu, and then click the Version tab in the Properties dialog box to view its current version number. Note that this number is 2.02.0002, and exit.

  8. On the Windows Start menu, click Run, and type in the following command, replacing the values within "<...>" with the actual paths on your system:

          <PATH TO VB5>\VB5.EXE /make <PATH TO Project1.VBP>\Project1.VBP
    

  9. Locate the Project1.exe file using the Microsoft Windows Explorer, right-click to select the file, click Properties on the menu, and then click the Version tab in the Properties dialog box. Note that the version number is 2.02.0003, as expected.

  10. On the Windows Start menu, click Run again and select the following

        command, which has the values within "<...>" replaced with the
        actual paths on your system:
    

          <PATH TO VB5>\VB5.EXE /make <PATH TO Project1.VBP>\Project1.VBP
    

  11. Locate the Project1.exe file using the Microsoft Windows Explorer,

        right-click to select the file, click Properties on the menu, and then
        click the Version tab in the Properties dialog box. Note that the
        version number is 2.02.0003 and has not changed. Compiling from the
        command line will no longer cause the Revision version number to be
        auto-incremented.
    


Additional query words: autoincremented
Keywords : VB4ALL VB4WIN vb5all VBKBDesignTime VBKBEnv VBKBVB
Version : WINDOWS:4.0,5.0
Platform : WINDOWS
Hardware : x86
Issue type : kbprb
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.