mattlittle
08-30-2005, 09:56 AM
I have multiple builds that are identical apart from version number. The version number gives the path to certain files.
I have a macro called INT_VERSION_NUMBER with a value of 5.3
I use this in several places. For example, I have another macro called log file location called LOG_PATH with the value D:\Builds\Phase%.INT_VERSION_NUMBER%\ From within a step, I can use the value %LOG_PATH % and it expands not only LOG_PATH, but the macro within it to so %LOG_PATH% equates to: D:\Builds\Phase5.3\
This works until I use VB Script to get the values of project macros, when it doesn't expand the inner macro (i.e. it gets the value as it is written e.g. D:\Builds\Phase%.INT_VERSION_NUMBER%\ as oppose to other steps that use this value that expand it correctly to D:\Builds\Phase5.3\)
How can I get the full expansion as oppose to just the 'first level' of expansion using code similar to this vb script:
Const LOG_FOLDER = "LOG_PATH"
Set LOG_FOLDER_STRING = projectmacros.Item(LOG_FOLDER )
Cheers
I have a macro called INT_VERSION_NUMBER with a value of 5.3
I use this in several places. For example, I have another macro called log file location called LOG_PATH with the value D:\Builds\Phase%.INT_VERSION_NUMBER%\ From within a step, I can use the value %LOG_PATH % and it expands not only LOG_PATH, but the macro within it to so %LOG_PATH% equates to: D:\Builds\Phase5.3\
This works until I use VB Script to get the values of project macros, when it doesn't expand the inner macro (i.e. it gets the value as it is written e.g. D:\Builds\Phase%.INT_VERSION_NUMBER%\ as oppose to other steps that use this value that expand it correctly to D:\Builds\Phase5.3\)
How can I get the full expansion as oppose to just the 'first level' of expansion using code similar to this vb script:
Const LOG_FOLDER = "LOG_PATH"
Set LOG_FOLDER_STRING = projectmacros.Item(LOG_FOLDER )
Cheers