To use PowerShell in FinalBuilder you need to have PowerShell 1.x installed on your machine. The download at the time of writing is:
Python support is included with FinalBuilder, using Microsoft's IronPython 2.0.
Active scripting based languages can be debugged using the Active Script Debugger, provided the language vendor supports debugging. To enable debugging you will need the Active Script Debugger installed, or Visual Studio.NET (which overrides the script debugger). PowerShell and Python script debugging is not yet possible.
FinalBuilder Script Events are Triggered Before and After an Action Executes. See Run Script action.
FinalBuilder variables are available in script events as global variables. You can reference them just as you would any other identifier. In PowerShell, you must access FinalBuilder variables with the following syntax:
$FBVariables.GetVariable(<variablename>) and $FBVariables.SetVariable(<variablename>)
Target Parameters are available in script events as global variables (same as FinalBuilder variables.)
|The external script file must be written in the same script language as the event handler script. FinalBuilder provides sample scripts to do things such as restart IIS, shut down COM+ components, etc.|
You can also use FinalBuilder variables in the path, for example : 'USEUNIT "%SCRIPTPATH%\Test.vbs"
|This is the only time you would use the %variable% syntax for FinalBuilder variables in the script editor, as the useunit line is preprocessed before the script is run.|
Entire action types can be written in Action Studio for inclusion in FinalBuilder.
PowerShell documentation can be found at the Windows PowerShell site:
Information about IronPython can be found at the IronPython home page on Codeplex: