PRB: Developer Studio Macro's ExecuteCommand Requires QuotesLast reviewed: February 20, 1998Article ID: Q181504 |
The information in this article applies to:
SYMPTOMSA VBScript macro ExecuteCommand method does not perform its specified command. Instead, it may perform an unexpected command or have no effect at all. Often, the macro generates no error messages.
CAUSEThe ExecuteCommand method takes one parameter--the keyword that Developer Studio will attempt to execute. If this keyword is not enclosed in quotation marks, the problems above may occur.
RESOLUTIONEnclose the command keyword following the ExecuteCommand method in quotation marks. If this does not correct the problem, verify that the command is valid:
ExecuteCommand "ProjectSettings"However, if there is no active project when the macro executes, that command will have no effect. For additional information, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q165681 TITLE : "INFO: Visual C++ 5.0 Readme, Build Issues" STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONAlways use quotation marks around the command keyword of ExecuteCommand. Developer Studio's behavior varies otherwise. Some commands, such as "Build", work without quotation marks. The "New" command generates a syntax error if it is not enclosed in quotation marks. Most commands perform no action at all when quotation marks are absent. The ExecuteCommand method requires a string parameter. This can be a literal string or a string variable. For example, the word "New" might be assigned to a string variable, such as "MyNewVar". This variable can then be used in place of "New" with the same result:
Dim MyNewVar MyNewVar = "New" ExecuteCommand MyNewVar REFERENCES"ExecuteCommand Method," Visual C++ Online Books
|
Additional query words: kbdsstools
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |