Within the Script field of a Run Script action, this is normal. That field is processed like another other step field: Any macros (%MACRO_NAME%) or script expressions ([code here]) are evaluated before using the field value.
http://www.visualbuild.com/Manual/stepproperties.htm
In the case of a Run Script action, the expanded value is then passed to a script host engine for parsing and execution.
This does not apply to code in the Script Editor, so if you wrap the code in a function, add it to, say, project scripts, and then call that function from a Run Script step, any macro references (within code or comments) in the Script Editor code will not be evaluated.
http://www.visualbuild.com/Manual/scripteditor.htm
02-14-2007, 12:22 PM
Hybrid Mode
