The information in this article applies to:
SYMPTOMSThe 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. CAUSEA 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:
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. MORE INFORMATIONSteps to Reproduce BehaviorTo reproduce the behavior, add a build command with an invalid command:
Additional query words:
Keywords : kbcode kbVC600 |
Last Reviewed: June 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |