...
One of the most asked for features now available in Automise 5, stepping into included projects. In Automise 7 and earlier, you could only step over included projects, and wait for them to return. In Automise 5, you can step into the included project, if it is not already opened the IDE will open the project and switch to it automatically. To make this possible, there are now "Step Into" and "Step Over" functions. The Step into/over now also applies to targets Action Lists (see below).
Debugger breakpoints now have conditions :
ActionLists renamed to Targets
ActionLists have been renamed to Targets. Targets can now also define dependencies, so you can for example define Clean, Build, Test, and have Test depend on Build. If you execute the Test target, and Build has not already been executed, it will be executed first before Test. Targets can be specified on the command line.
In Automise 7 and earlier, projects had a Main and an OnFailure (global error handler) actionlist. In Automise 5, projects just have a Default Target. Older projects will be imported such that the Main and OnFailure Targets are called from the Default Target inside a try/catch block.
...
Run Action List Action
You can now return values from Targets Action Lists (ie out parameters) .
Non Visible Changes
...
The stepping engine was rewritten to enable stepping into included projects, and to enable target Action List dependencies. This, work, together with the new variables architecture is where the bulk of effort/time was spent in the Automise 5 development cycle.
...
The command line parameters have changed to be more consistent and easier to specify. You can also specify one or more targets Action Lists to execute (when not specified, the default target Action List is executed).
New Project File Formats
...