|
#1
|
|||
|
|||
VBP implements an order of precedence (temporary, project, global, system [highest to lowest]) when macros are referenced like %MACRO_NAME% within step fields (or like Application.ExpandMacrosAndScript("%MACRO_NAME%") within script code), and overriding a project macro (which defines the default) with a temporary macro (on the command-line) is an ideal use of this feature. See the following help topics/samples for more details:
http://www.visualbuild.com/Manual/?macrostab.htm http://www.visualbuild.com/Manual/?hints.htm (3rd from last bullet) http://www.visualbuild.com/Manual/?v...dprosample.htm |
#2
|
|||
|
|||
Quote:
|
#3
|
|||
|
|||
Only temporary macros can be created on the command-line. You could add a Run Script step to create/update a project macro for each temporary macro. See the attached sample.
But normally you would not want to modify a project within a build, because Visual Build will prompt for changes on exit. http://www.kinook.com/Forum/showthread.php?t=245 |
|
|