deramor
10-04-2011, 01:44 PM
Hello-
I am using the Write XML project step to remove Source Safe information from Visual Studio project files. I basically find the XML fields and NULL them.
This works fine when the project file I am looking at has source control information in it. When this information is not present, the XML fields are not there for me to NULL. This causes the step to fail since the XPath I used was not found. The step failure is not important to me for this reason but for other reasons it would be. Is there any way to have this step continue when the XPath is not found but fail in all other cases?
Simply marking the step to continue and not execute failure steps is not a good alternative.
I have in the past edited a single step's script to pass a step for a particular exit code:
Sub vbld_StepDone()
If CLng(Application.ExpandMacros("%RUNPROGRAM_EXITCODE%")) = -1073741819 Then
Step.BuildStatus = vbldStepStatSucceeded
End If
End Sub
However I see no macro that is created with an exit code for me to work with in this instance. The above edit was to work around a problem with InstallShield which apparently uses the run program project step underneath which in turn generates the %RUNPROGRAM_EXITCODE% macro as part of its execution. I do see the LASTSTEP_STATUS but it seems to be only a pass/fail value rather than an exit code.
Thanks-
Rob
I am using the Write XML project step to remove Source Safe information from Visual Studio project files. I basically find the XML fields and NULL them.
This works fine when the project file I am looking at has source control information in it. When this information is not present, the XML fields are not there for me to NULL. This causes the step to fail since the XPath I used was not found. The step failure is not important to me for this reason but for other reasons it would be. Is there any way to have this step continue when the XPath is not found but fail in all other cases?
Simply marking the step to continue and not execute failure steps is not a good alternative.
I have in the past edited a single step's script to pass a step for a particular exit code:
Sub vbld_StepDone()
If CLng(Application.ExpandMacros("%RUNPROGRAM_EXITCODE%")) = -1073741819 Then
Step.BuildStatus = vbldStepStatSucceeded
End If
End Sub
However I see no macro that is created with an exit code for me to work with in this instance. The above edit was to work around a problem with InstallShield which apparently uses the run program project step underneath which in turn generates the %RUNPROGRAM_EXITCODE% macro as part of its execution. I do see the LASTSTEP_STATUS but it seems to be only a pass/fail value rather than an exit code.
Thanks-
Rob