User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
 

Debugging a simple script with a few lines is not a big deal, hit debug and step through it. Almost any PowerShell related editor can do that today. But what if you need to debug a complete system of scripts interacting with one another? PrimalScript has the ability to debug multiple scripts.

Sure you could type Set-PSBreakPoint –script filename.ps1 –line xxx as needed and launch the whole thing from the command line, but let’s face it, if you do that more than twice it gets a bit old.

PrimalScript already saves your breakpoints with your files, so once you set them they are just there. Now, just open the files you need and select the new “Debug Multiple Scripts” topic.

Debug Multiple Scripts

Select the startup file and the secondary files accordingly:

Select the startup file and the secondary files

And click OK. That’s it, the debugger will now just pace through your files and stop at your breakpoints:

the debugger will pace through your files and stop at your breakpoints

Hitting the first breakpoint in our startup file

 

Hitting the breakpoint in the second file

Hitting the breakpoint in the second file

 

Hitting the breakpoint in the third file

And a third file

 

Hitting the breakpoint in another file

And one more file down the chain

 

back at the second breakpoint in the startup file

And back at the second breakpoint in the startup file.

 

Now it is pretty easy to make modifications and repeatedly debug the entire system.


This feature requires PrimalScript v6.5.132 or higher.
This will also be supported in PowerShell Studio v3.1.9 or higher.

If you have questions about our products, please post in our support forum.
For licensed customers, use the forum associated with your product in our Product Support Forums for Registered Customers.
For users of trial versions, please post in our Trial Software Questions forum.
Copyright © 2017 SAPIEN Technologies, Inc.