Kinook Software Forum

Go Back   Kinook Software Forum > Visual Build Professional > [VBP] General Discussion
Register FAQ Community Calendar Today's Posts Search

 
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #6  
Old 04-24-2014, 05:39 PM
deramor deramor is online now
Registered User
 
Join Date: 05-11-2011
Posts: 27
Quote:
Originally Posted by kinook View Post
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
I realize this is an old topic but I couldn't find an answer to my question and this thread was the closest I could get. I attempted to pass a value on the command line to change the value of a project macro. However this method caused a temporary macro to be created instead. From reading the thread and the links this is expected. Is there any way other than some workaround (registry/external file) to define a project macro on the command line?
Reply With Quote
 


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 05:05 PM.


Copyright © 1999-2023 Kinook Software, Inc.