Microsoft KB Archive/183418

= BUG: Build Succeeds Despite Invalid Custom Build Command =

Article ID: 183418

Article Last Modified on 12/8/2003

-

APPLIES TO


 * Microsoft Visual C++ 5.0 Enterprise Edition
 * Microsoft Visual C++ 6.0 Enterprise Edition
 * Microsoft Visual C++ 5.0 Professional Edition
 * Microsoft Visual C++ 6.0 Professional Edition
 * Microsoft Visual C++ 6.0 Standard Edition

-



This article was previously published under Q183418



SYMPTOMS
The message "Bad command or file name" shows up in the Build pane. On Windows NT, the build fails with an error. However, on Windows 95 the project may still build with no errors indicated.



CAUSE
A custom build step references a non-existent executable. The command interpreters for Windows 95 and Windows NT, which spawn the custom build command, respond differently for non-existent executables.



RESOLUTION
The following are two possible resolutions:


 * Make the custom build command refer to a valid file.
 * Create an application that spawns other executables, and have it return an error code on failure to load.



STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.



Steps to Reproduce Behavior
To reproduce the behavior, add a build command with an invalid command:


 * 1) Create a Win32 Console Application.
 * 2) On the Project menu, click Settings, and click the Custom Build Tab.
 * 3) For Build Command(s), enter Bogus.exe.
 * 4) For Output File(s), enter X.out.
 * 5) Click OK to save the settings.
 * 6) Build the project on Windows 95.

Keywords: kbbug kbpending kbcode KB183418

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.