|
Thank you.
I looked at the example and this is what I came up with. I am using two 'Run Script' action steps. The first one gets the version number of a file and set it to the project macro VER_NUM, as shown below.
Set objMacro = Application.Macros(vbldProject).Item("VER_NUM")
objMacro.Value = vbld_FSO.GetFileVersion("path")
The second step gets that number and increments it; both steps are simple.
I have to use two steps because when I check to see if the previous version number was overwritten after the first step is build, the macro still has the old version number. However, I only call the macro on the second step, and it increments it, that being the new retrieved number. Even though the old number is shown after the first step is build, in reality, the new number replaced it, right? Is there a one step delay in this process? Will the new number be displayed on the macros and output pane once a 'Run Script" step using that macro is ran again? Because that's what's happening.
I also combined the two, and now the macro value is updated on the macros pane, but when it logs the message on the output pane, is still displays the old version number. Is there a way around this?
Thank you for your help.
|